campaignstack

campaignstack_estimate_cost

Read-onlyIdempotent

What a costed 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. Call this when the user is about to run a costed tool at volume and wants the exposure first; it only calculates, never reserves or spends. A paid workspace overflows to overage and reports a null balance rather than a refusal. The price comes from the same table the charge is made from, so it can never drift from what you are billed. Call it before a batch: the unit for a tool is a call, a result found or a page read, and the difference is a month of credits.

Input Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes	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.
`count`	No	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.
`workspaceId`	No	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.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that the tool only calculates and never reserves or spends, that paid workspaces overflow to overage with a null balance instead of a refusal, and that pricing comes from the same table as billing. These traits materially affect interpretation of results.

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?

The purpose and return values are front-loaded, with later sentences adding useful edge-case and pricing context. The closing clause 'the difference is a month of credits' is unclear, but the overall structure is tight.

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

Completeness5/5

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

Given the output schema, annotations, and parameter schema, the description supplies the missing behavioral and edge-case context needed to invoke and interpret the tool. Nothing essential for correct selection or calling appears absent.

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

Parameters3/5

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

The schema already has 100% parameter coverage, including what a unit means and workspaceId behavior, so the baseline applies. The description reinforces the unit concept but does not add meaningful parameter information beyond the schema.

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?

The description states a clear action and object: it estimates what a costed tool would spend before invocation, and enumerates the returned fields. This is distinct from execution or balance-lookup siblings, so an agent can tell when this pre-call estimator is relevant.

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?

It explicitly says to call this before running a costed tool at volume or before a batch, to expose spend risk first. It does not name an alternative tool or say when not to use it, but the conditions are specific enough to route usage.

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?