Skip to main content
Glama

ADS Beast

campaign_draft_publish_check

Read-only

Validates a campaign draft against the live ad account and reports exactly what publishing would create or change. Read-only rehearsal: nothing is written.

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": {
      "client_id": "<client_id>",
      "build_id": "<build_id>"
    },
    "name": "campaign_draft_publish_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_idYesDraft id from list_campaign_drafts.
client_idYes
platform_campaign_idNoExisting platform campaign to complete instead of creating a new one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is structured data; the description reinforces it with a plain-language 'nothing is written' guarantee. It adds genuine context beyond the annotations by saying the check runs 'against the live ad account' and reports the concrete create/change deltas that publishing would produce. It does not mention auth requirements or any rate/latency constraints, which keeps it short of a 5.

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 short sentences with zero filler, and the core assertion ('validates ... reports what publishing would create or change') is front-loaded before the read-only reassurance. Nothing could be removed without losing information.

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?

For a three-parameter read-only rehearsal with no output schema, the description covers what the tool does, what it acts on, and what kind of answer it returns. The remaining gap is the undocumented client_id and the absence of any hint about the report's shape, which matters somewhat given no output schema exists.

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

Parameters2/5

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

Schema coverage is only 67%: build_id and platform_campaign_id carry descriptions in the schema, but client_id is undocumented in both places. The description adds no parameter meaning at all, not even explaining that omitting platform_campaign_id means a new campaign is created. With a meaningful coverage gap and zero compensating text, the description leaves the agent to infer the parameter behavior.

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?

The description uses a specific verb and resource: 'Validates a campaign draft against the live ad account and reports exactly what publishing would create or change.' That makes the purpose unmistakable and the 'read-only rehearsal' framing separates it conceptually from an actual publish step. It does not name the closest sibling (prepare_campaign_draft_publish), leaving the final distinction to be inferred from the name alone.

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?

'Read-only rehearsal: nothing is written' implies this belongs before a publish action, and the phrase 'what publishing would create or change' frames the moment of use. There is no explicit when-to-use or when-not statement, and no named alternative for the case where the agent actually wants to publish or wants draft details only, so the guidance stays implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.