StealAds

Review a campaign output

get_campaign_output_workspace

Read-onlyIdempotent

Returns one finished campaign image with its versions: the available version ids, the selected version, the ad copy and the saved placement sizes. The read that precedes select_campaign_output_version and get_campaign_export_descriptor. Read-only: generates, resizes and exports nothing. Works for completed outputs created by this account.

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": {
      "campaign_id": "<campaign_id>",
      "generation_job_id": "<generation_job_id>"
    },
    "name": "get_campaign_output_workspace"
  }
}

Input Schema

Name	Required	Description
`campaign_id`	Yes	campaign_id from list_campaigns.
`response_format`	No	Output format: text (default) or json. table is not available for this tool.
`generation_job_id`	Yes	The image's finished-image reference: _references.generation_job_id on a get_campaign_outputs or list_campaigns result.

Output Schema

Name	Required	Description
`copy`	No	copy value in this response.
`sizes`	No	sizes value in this response.
`versions`	No	versions value in this response.
`cta_status`	No	cta status value in this response.
`_references`	No	Opaque action references accepted by subsequent tool calls.
`campaign_id`	No	campaign id value in this response.
`selection_state`	No	selection state value in this response.
`selected_version_id`	No	selected version id value in this response.
`quality_review_recommended`	No	quality review recommended value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

changedInput schema / properties / campaign_id / description

Previous value: -"Campaign reference from list_campaigns."New value: +"campaign_id from list_campaigns."

changedInput schema / properties / generation_job_id / description

Previous value: -"Generated image reference from list_generation_jobs or get_campaign_outputs."New value: +"The image's finished-image reference: _references.generation_job_id on a get_campaign_outputs or list_campaigns result."

changedInput schema / properties / response_format / description

Previous value: -"Output format: text or json for capped research examples; table is available only for tracked rival rows."New value: +"Output format: text (default) or json. table is not available for this tool."

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description adds context beyond annotations by specifying what is NOT done: "generates, resizes and exports nothing." This clarifies the read-only nature beyond the readOnlyHint annotation, and specifies scope: "Works for completed outputs created by this account." This behavioral disclosure is useful with no contradictions.

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?

The description is concise and front-loaded with what is returned, followed by workflow guidance and behavioral constraints. All sentences serve a purpose. It could be tightened further but is efficient.

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?

Given the output schema exists and there are detailed schema descriptions for 3 parameters, the description rounds out contextual needs with return content overview and workflow sequencing. The scope limitation to completed outputs from this account is critical. Complete for this complexity level.

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% with descriptions for campaign_id, generation_job_id, and response_format. The description doesn't add additional parameter meaning beyond what the schema provides, which is expected and fine. Baseline 3 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 uses a very specific verb + resource + field set: "Returns one finished campaign image with its versions: the available version ids, the selected version, the ad copy and the saved placement sizes." An agent can distinguish this from siblings like get_campaign_outputs (list) and select_campaign_output_version (mutate).

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?

The description explicitly places this tool in a workflow, stating it is "the read that precedes select_campaign_output_version and get_campaign_export_descriptor." This gives clear sequencing guidance. It lacks explicit when-not-to-use exclusion, but the read-before-write framing is strong.

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

All StealAds tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.