Skip to main content
Glama

ADS Beast

prepare_campaign_draft_publish

Prepare creating a full campaign in Google Ads or Meta from a campaign draft. The campaign is created PAUSED: it does not serve and spends nothing until a person enables it separately. The preview carries the rehearsal against the live account. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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>",
      "reason": "<reason>"
    },
    "name": "prepare_campaign_draft_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
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

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the created campaign is PAUSED and serves/spends nothing until a person enables it, the preview is rehearsed against the live account, nothing changes at prepare time, and the preview_id expires in 15 minutes and is single-use. The annotations (destructiveHint=false) are consistent with this no-change staging claim.

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 the safety guarantee (PAUSED, no spend), then the no-change preview and expiry. Four dense sentences with no filler, though the final clause is telegraphic enough that 'to show, then execute_prepared_change' reads as a fragment.

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?

No output schema exists, yet the description explains what the preview contains (a rehearsal against the live account), what is returned (preview_id with 15-minute, single-use lifetime), and how to continue. For a staging tool with four parameters this covers everything an agent needs to call it correctly.

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 coverage is 75% and the description only implies that build_id refers to a draft; it does not clarify platform_campaign_id's completion-vs-create semantics, which the schema description does cover. It adds little meaning beyond the schema, so the baseline applies.

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 names a specific verb (prepare creating) and resource (a full campaign in Google Ads or Meta) sourced from a campaign draft, and distinguishes the tool from the actual execution step by naming execute_prepared_change. An agent can tell it is a staging step rather than a mutation or a validation check.

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?

Clear usage context: this tool only prepares and stores a preview_id, and the agent is told the follow-up is execute_prepared_change after showing the preview to a person. It does not explicitly disambiguate from campaign_draft_publish_check or the other prepare_* tools, so the when-to-use is strong on the next step but not on sibling selection.

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.