campaignstack

campaignstack_estimate_cost

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description
`tool`	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.
`count`	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.
`variant`	No	For multi-cost tools, estimate one variant by name (for example email, phone, audit, probe, serp).
`workspaceId`	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.
`variantCounts`	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}.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`per`	No
`note`	No
`tool`	No
`count`	No
`label`	No
`total`	No
`isPaid`	No
`allowed`	No
`balance`	No
`variant`	No
`variants`	No
`actionType`	No
`creditsPerUnit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"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."

Changed7 schema fields changedSep 26, 2026

changedInput schema / properties / count / description

Previous value: -"How many units you are about to spend. What a unit IS depends on the tool (a call, a result found, a page read); the response repeats it as `per`. Default 1."New value: +"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."

changedInput schema / properties / tool / description

Previous value: -"A costed tool name, e.g. campaignstack_craft_message. Known costed tools: campaignstack_analyze_website, campaignstack_answer_job_question, campaignstack_apply_to_job, campaignstack_check_company_news, campaignstack_comment_on_post, campaignstack_craft_comment, campaignstack_craft_followup, campaignstack_craft_message, campaignstack_craft_note, campaignstack_discover_lead_magnets, campaignstack_draft_meeting_message, campaignstack_enrich_lead_contact_info, campaignstack_explain_draft, campaignstack_extract_conversation_voice, campaignstack_extract_recent_comments, campaignstack_follow_profile, campaignstack_like_post, campaignstack_refresh_company, campaignstack_regenerate_playbook, campaignstack_reply_to_comment, campaignstack_request_meeting_brief, campaignstack_reread_review_link, campaignstack_send_connection_request, campaignstack_send_gmail, campaignstack_send_inmail, campaignstack_send_message, campaignstack_seo_run_audit."New value: +"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."

addedInput schema / properties / variant

Added value: +{
+  "description": "For multi-cost tools, estimate one variant by name (for example email, phone, audit, probe, serp).",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / variantCounts

Added value: +{
+  "additionalProperties": {
+    "maximum": 100000,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "description": "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}.",
+  "type": "object"
+}

addedOutput schema / properties / label

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / variant

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / variants

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "actionType": {
+                "type": "string"
+              },
+              "allowed": {
+                "type": "boolean"
+              },
+              "balance": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "count": {
+                "type": "number"
+              },
+              "creditsPerUnit": {
+                "type": "number"
+              },
+              "isPaid": {
+                "type": "boolean"
+              },
+              "label": {
+                "type": "string"
+              },
+              "note": {
+                "type": "string"
+              },
+              "per": {
+                "type": "string"
+              },
+              "total": {
+                "type": "number"
+              },
+              "variant": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / tool / description

Previous value: -"A costed tool name, e.g. campaignstack_craft_message. Known costed tools: campaignstack_analyze_website, campaignstack_check_company_news, campaignstack_comment_on_post, campaignstack_craft_comment, campaignstack_craft_followup, campaignstack_craft_message, campaignstack_craft_note, campaignstack_discover_lead_magnets, campaignstack_draft_meeting_message, campaignstack_enrich_lead_contact_info, campaignstack_explain_draft, campaignstack_extract_conversation_voice, campaignstack_extract_recent_comments, campaignstack_follow_profile, campaignstack_like_post, campaignstack_refresh_company, campaignstack_regenerate_playbook, campaignstack_reply_to_comment, campaignstack_request_meeting_brief, campaignstack_reread_review_link, campaignstack_send_connection_request, campaignstack_send_gmail, campaignstack_send_inmail, campaignstack_send_message, campaignstack_seo_run_audit."New value: +"A costed tool name, e.g. campaignstack_craft_message. Known costed tools: campaignstack_analyze_website, campaignstack_answer_job_question, campaignstack_apply_to_job, campaignstack_check_company_news, campaignstack_comment_on_post, campaignstack_craft_comment, campaignstack_craft_followup, campaignstack_craft_message, campaignstack_craft_note, campaignstack_discover_lead_magnets, campaignstack_draft_meeting_message, campaignstack_enrich_lead_contact_info, campaignstack_explain_draft, campaignstack_extract_conversation_voice, campaignstack_extract_recent_comments, campaignstack_follow_profile, campaignstack_like_post, campaignstack_refresh_company, campaignstack_regenerate_playbook, campaignstack_reply_to_comment, campaignstack_request_meeting_brief, campaignstack_reread_review_link, campaignstack_send_connection_request, campaignstack_send_gmail, campaignstack_send_inmail, campaignstack_send_message, campaignstack_seo_run_audit."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "actionType": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "allowed": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "balance": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "count": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "number"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "creditsPerUnit": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "number"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "isPaid": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "note": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "per": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "tool": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "total": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "number"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 13, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint/idempotentHint already declared, the description adds real value beyond annotations: it never reserves or spends, prices come from the same table as the charge, overage yields a null balance rather than a refusal, and it refuses to guess for multi-mode tools. These are non-obvious behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then behaviors, then parameter-routing rules; each sentence carries information. The opening 'What a costed final MCP tool would spend' is slightly awkward but functional. Dense without real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still usefully previews the return (creditsPerUnit, total, remaining balance, allowed) and edge behaviors (overage, null balance). Complex tool with a rich schema is adequately covered; only the invalid-tool-name error path is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds the semantic rule that matters: use variant for one mode and variantCounts for full exposure, and clarify that 'count' is per-unit versus the 'per' returned. This exceeds what the schema alone conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('estimate cost' / 'What a costed final MCP tool would spend') and immediately bounds the scope ('before you call it'). It is clearly a pre-flight calculator, distinct from all the action siblings it can price.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tells the agent when to invoke it ('before you call it') and how to handle multi-charge-mode tools via variant vs variantCounts, noting the tool 'refuses to guess' otherwise. It stops short of explicitly naming a when-not case or a sibling alternative, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All campaignstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?