Skip to main content
Glama

ADS Beast

get_campaign_draft

Read-only

The current content of one build and a fresh validation: 'problems' block publishing, 'warnings' do not, 'launch_blockers' say why a person could not publish right now (no connected account, writing switched off), 'not_checked_here' lists what only the publish step checks. Problem texts come from the builder's own checker and are in Russian; relay them in the user's language.

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_idYesBuild id from list_campaign_drafts or create_campaign_draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuine behavior beyond them: a validation is re-run on each call ('fresh validation'), the severity semantics of each block are explained, and the Russian-language origin of checker texts is disclosed along with the instruction to relay them in the user's language. It stops short of covering permissions, latency/cost of the fresh validation, or how the draft content itself is shaped.

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?

One dense but well-ordered sentence: the main assertion comes first, then the validation blocks in the order an agent would triage them. The quoting of block names is compact rather than wasteful, though the run-on construction makes it slower to scan than it needs to be.

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 read-only, single-parameter tool with no output schema, the description goes a long way toward describing the return value by enumerating the validation blocks and their severity meanings. The remaining gap is the shape of the 'current content' portion of the response, which is not characterized at all.

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?

There is a single parameter and schema coverage is 100%, with the schema itself stating 'Build id from list_campaign_drafts or create_campaign_draft.' The description adds nothing about draft_id, so the baseline 3 applies.

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 names the resource precisely: the current content of one build plus a fresh validation, and breaks the validation into named blocks (problems, warnings, launch_blockers, not_checked_here). It implicitly separates itself from the publish path by saying 'not_checked_here' lists only what the publish step checks, but it never names the sibling that performs that publish check outright.

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: the detail about launch_blockers ('why a person could not publish right now') hints that this is a pre-publish inspection tool. There is no explicit when-to-use statement, no when-not, and no named alternative such as campaign_draft_publish_check or campaign_draft_details.

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.