Skip to main content
Glama

ADM Google Ads

Get an AI new-campaign draft

get_campaign_draft
Read-onlyIdempotent

Returns the state of a draft started by draft_campaign: pending, running, done or failed. When done, campaign can be passed verbatim to create_search_campaign (preview first). If missing_fields is not empty (usually campaign.daily_budget), ask the user, set those fields on campaign, then preview. keyword_planner_used tells whether Google Keyword Planner data was used; when true, keyword_metrics lists avg_monthly_searches and competition for the draft's keywords (close_variants share the same row's combined numbers). When failed, error explains why; start a new draft. Drafts are kept for 24 hours.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "get_campaign_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYesdraft_id returned by draft_campaign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds substantial behavioral context beyond annotations: the full state machine, how missing_fields should be handled, what keyword_planner_used and keyword_metrics mean, how failures are reported, and that drafts expire after 24 hours. It does not contradict the read-only annotation.

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?

The description is dense but well front-loaded: it leads with the returned state before moving to state-dependent workflows. Every sentence carries operational meaning, including retention and keyword-planner semantics, with no filler. Semicolon-heavy phrasing is compact rather than wasteful.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so by naming state, campaign, missing_fields, keyword_planner_used, keyword_metrics, and error. It also covers the complete action workflow for each terminal state and the 24-hour lifetime. For a one-parameter read tool with rich annotations, nothing essential is missing.

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 100% and the sole parameter draft_id is already documented as the identifier returned by draft_campaign. The description reinforces that this identifies the draft created by the sibling tool but does not add syntax, format, or validation details beyond the schema. A baseline 3 is appropriate when the schema fully documents the only parameter.

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 opens with a specific verb and resource: it returns the state of a draft started by draft_campaign. It explicitly distinguishes the draft lifecycle from the draft-creation sibling and enumerates the possible states. An agent can immediately tell this is the polling/status tool for campaign drafts.

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 gives explicit next-step guidance for each state: pass campaign verbatim to create_search_campaign when done, preview first, ask the user to populate missing_fields, or start a new draft when failed. The alternative workflows are named with their conditions, leaving little to inference. This is unusually strong routing guidance for a status tool.

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.

Resources