Account & Capabilities
Check who you are, what the platform can do, and what an action will cost before running it.
Tools (4)
Section titled “Tools (4)”estimate_cost
Section titled “estimate_cost”Full name: campaignstack_estimate_cost
What a costed final MCP tool would spend, before you call it. Returns creditsPerUnit, the total for the count you name, the workspace’s remaining free balance, and whether the spend is allowed. It only calculates, never reserves or spends. A paid workspace overflows to overage and reports a null balance rather than a refusal. Prices come from the same table the charge is made from, so single-action tools cannot drift from billing. For tools with multiple charge modes, pass variant for one mode or variantCounts for the full exposure; otherwise the tool refuses to guess.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
tool | string | Yes | — | A costed final tool name, e.g. campaignstack_craft_message. Known costed tools: campaignstack_analyze_company_website, campaignstack_answer_job_question, campaignstack_apply_to_job, campaignstack_comment_on_post, campaignstack_craft_message, campaignstack_decide_review, campaignstack_discover_lead_magnets, campaignstack_enrich_leads, campaignstack_explain_draft, campaignstack_export_seo_report, campaignstack_follow_profile, campaignstack_get_lead_comments, campaignstack_like_post, campaignstack_prepare_meeting_brief, campaignstack_refresh_companies, campaignstack_refresh_identity_voice, campaignstack_refresh_workspace_playbook, campaignstack_run_seo_audit, campaignstack_send_connection_request, campaignstack_send_email, campaignstack_send_inmail, campaignstack_send_message. (min length: 1) |
variant | string | No | — | For multi-cost tools, estimate one variant by name (for example email, phone, audit, probe, serp). (min length: 1) |
variantCounts | object | No | — | For multi-cost tools, estimate multiple variants at once. Keys are variant names and values are unit counts, e.g. {audit:1, probe:30, serp:10}. |
count | integer | No | — | How many units you are about to spend for a single-cost tool or one selected variant. What a unit IS depends on the tool (a call, a result found, a page read); the response repeats it as per. Default 1. (min: 1, max: 100000) |
workspaceId | string | No | — | Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too. |
explain_capabilities
Section titled “explain_capabilities”Full name: campaignstack_explain_capabilities
Explain how the pieces of this workspace fit together, so you can pick the right tool without opening several to compare them. Call this when you are choosing between similar tools, when a request does not obviously map to one tool, or when an error tells you to consult it. topic: overview (default), watchers (how to choose between the eight ways to monitor something), workflows (how a workflow gets its leads, and which tool creates which kind), platforms (what can be acted on and what is tracking-only), outreach_and_safety (who sends, what the limits are, and what to confirm with the user first). It is a static reference and returns no live counts: each topic names the list tool that does (campaignstack_get_signal_agents, campaignstack_get_workflows, and so on). Costs nothing and reads no workspace data.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
topic | overview | watchers | outreach_and_safety | platforms | workflows | No | — | Which map to return. Defaults to overview. |
get_platform_capabilities
Section titled “get_platform_capabilities”Full name: campaignstack_get_platform_capabilities
Lists every platform action (like_post, comment_on_post, follow_profile, send_message, send_connection_request, send_inmail, extract_post_engagements) with the platforms it supports and, per platform, the accepted target fields and optional params. Returns platforms, which says for each platform whether accounts can be connected, how many this workspace has, and which actions exist there: a platform with no actions is tracking-only by design, not unfinished. connectedPlatforms is the older shape and lists only platforms with a connected account. Call this when an action tool returns wrong_target_for_platform or unsupported_capability.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
workspaceId | string | No | — | Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too. |
whoami
Section titled “whoami”Full name: campaignstack_whoami
Who this connection is and what it may do: the workspace it is bound to, the permissions the owner approved, and whether it is an API key or a connected app. Call it when a tool asks which workspace a call is for (a person in several workspaces names one; with only one, workspaceId defaults to it), and use campaignstack_explain_capabilities when the question is which tool to reach for rather than what is permitted. It reads nothing about leads or campaigns.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
include | object | No | {} | |
include.notificationPreferences | boolean | No | false |