campaignstack

Get lead refresh status

campaignstack_get_lead_refresh_status

Read-onlyIdempotent

Read workspace lead-enrichment queue status counts, optionally for one campaign. Use this when the user asks whether lead refresh/enrichment is moving; it does not enqueue refreshes. completed and failed cover about the last 6 hours, not all time.

Input Schema

Name	Required	Description	Default
`campaignId`	No	Optional campaign filter for enrichment queue status.
`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.

Output Schema

Name	Required	Description
`items`	No
`total`	No
`failed`	No	Failed in about the last 6 hours; older rows are purged.
`pending`	No
`stranded`	No	Part of pending held on an account that can no longer read (disconnected, expired or blocked); these move to another account or fail on their own.
`warnings`	No
`completed`	No	Finished in about the last 6 hours; older rows are purged, so this is not a lifetime count.
`pagination`	No
`processing`	No
`accountGates`	No
`creditsExhausted`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

addedOutput schema / properties / completed / description

Added value: +"Finished in about the last 6 hours; older rows are purged, so this is not a lifetime count."

addedOutput schema / properties / failed / description

Added value: +"Failed in about the last 6 hours; older rows are purged."

addedOutput schema / properties / stranded

Added value: +{
+  "description": "Part of pending held on an account that can no longer read (disconnected, expired or blocked); these move to another account or fail on their own.",
+  "type": "number"
+}

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."

AddedSep 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds genuinely non-structured context: completed and failed counts cover roughly the last 6 hours rather than all time, a caveat that meaningfully changes interpretation of the numbers.

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

Conciseness5/5

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

Two sentences, zero filler, with the core read operation and its scope front-loaded before the usage routing and the time-window caveat.

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?

With an output schema covering the returned counts and annotations covering safety, the only thing an agent could get wrong is the semantic window of the counts and whether this triggers work – both are addressed explicitly.

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?

Schema description coverage is 100%, including a detailed explanation of workspaceId resolution and the optional campaignId filter, so the baseline is 3. The description adds only the phrase 'optionally for one campaign' beyond what the schema already says.

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 gives a specific verb and resource ('Read workspace lead-enrichment queue status counts') and qualifies scope ('optionally for one campaign'), then explicitly separates the tool from the enqueue path with 'it does not enqueue refreshes', distinguishing it from campaignstack_refresh_leads.

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

Usage Guidelines5/5

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

It states exactly when to reach for it ('when the user asks whether lead refresh/enrichment is moving') and when not to ('it does not enqueue refreshes'), implicitly routing enqueue requests to the refresh tool. Both the positive and negative conditions are present.

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?