Skip to main content
Glama

ADS Beast

campaign_draft_details

Read-only

A campaign draft in full: platform, type, goal, budget, UTM, targeting, ad groups with keywords and ads, and the platform campaign id once it was published.

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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_idYesDraft id from list_campaign_drafts.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by enumerating the payload and noting the platform campaign id exists only 'once it was published', which tells the agent how to infer publication state. It does not mention client scoping, failure modes for unknown ids, or authentication.

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?

A single front-loaded sentence that lists the returned fields without filler. The field enumeration is long but each item carries information, though it reads more like a return-value summary than a statement of purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully substitutes for one by describing the shape of the returned draft. It is still incomplete for a two-parameter lookup: client_id is unexplained and nothing is said about behavior when the build_id does not exist or belongs to another client.

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?

The description mentions no parameters at all. With only 50% schema coverage, build_id is documented in the schema ('Draft id from list_campaign_drafts') but client_id is undocumented in both places, and the description does nothing to compensate for that gap or clarify how client_id scopes the lookup.

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

Purpose3/5

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

The description conveys the resource ('a campaign draft in full') and enumerates its contents, so an agent can tell this returns detailed draft data. However, there is no explicit verb (fetch/retrieve) and no differentiation from the near-identically named sibling get_campaign_draft, leaving the boundary between the two ambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no mention of alternatives such as list_campaign_drafts or get_campaign_draft. The only routing hint ('Draft id from list_campaign_drafts') lives in the input schema, not the description.

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.