FeedSquad

Confirm Campaign

confirm_campaign

DestructiveIdempotent

Approves all or cancels all posts in a campaign. Approving does not need the platforms connected; the response's connections lists each platform that is not, and its posts publish at their times if it is connected by then.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaign_id": "<campaign_id>",
      "action": "<action>"
    },
    "name": "confirm_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes	Action to take: approve_all or cancel_all
`campaign_id`	Yes	The campaign ID to confirm

Output Schema

Name	Required	Description	Default
`kind`	Yes
`name`	Yes
`posts`	Yes
`theme`	No
`notice`	No
`status`	Yes
`progress`	No
`campaign_id`	Yes
`connections`	No
`description`	No
`quota_notice`	No
`dashboard_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: approving works without platforms connected, the response's connections field enumerates unconnected platforms, and posts will publish at their scheduled times if a platform is connected by then. It still does not say whether cancel_all is reversible or what happens to already-published posts.

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?

Only two sentences and the primary action is front-loaded. The second sentence is slightly convoluted—'lists each platform that is not' reads as an incomplete clause—but no sentence is wasted.

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?

Output schema exists so return values need not be spelled out, yet the description still explains the key part of the response (the connections list). Annotations cover the destructive/idempotent profile, and the platform-connection caveat fills the main behavioral gap for a two-parameter confirmation tool.

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% and the action enum is documented in the schema, so the schema carries the parameter burden. The description's 'approves all or cancels all' loosely maps to the two enum values but adds no format or constraint details for campaign_id.

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

Purpose4/5

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

States a specific verb pair and resource: approves all or cancels all posts in a campaign. Clear enough to distinguish from the sibling confirm_post (single post) by the explicit 'in a campaign' scoping, though it never names that sibling.

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

Usage Guidelines3/5

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

Usage is only implied by the action semantics; there is no explicit 'use this when' or exclusion versus confirm_post, archive_posts, or create_campaign. The note that approving does not require connected platforms is useful context for deciding whether to call now, but it is not framed as guidance.

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

All FeedSquad 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?