StealAds

Select a campaign output version

select_campaign_output_version

Idempotent

Makes an existing image version the selected one for a campaign image. Takes the target version_id and expected_current_version_id, both from get_campaign_output_workspace; when the selection has changed since that read the call is refused, so a stale choice cannot overwrite a newer one. Selecting the version that is already selected changes nothing. Generates and exports nothing.

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>",
      "version_id": "<version_id>",
      "expected_current_version_id": "<expected_current_version_id>"
    },
    "name": "select_campaign_output_version"
  }
}

Input Schema

Name	Required	Description
`version_id`	Yes	Version id to select, from get_campaign_output_workspace.
`campaign_id`	Yes	campaign_id from list_campaigns.
`generation_job_id`	Yes	The image's finished-image reference: _references.generation_job_id on a get_campaign_outputs or list_campaigns result.
`expected_current_version_id`	Yes	Version id that get_campaign_output_workspace reported as selected; a selection that changed since that read is refused.

Output Schema

Name	Required	Description
`copy`	No	copy value in this response.
`sizes`	No	sizes value in this response.
`changed`	No	changed 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.
`cost_credits`	No	Credits quoted or charged by this operation.
`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.

Changed4 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 / expected_current_version_id / description

Previous value: -"Selected version reference from get_campaign_output_workspace; rejects stale changes."New value: +"Version id that get_campaign_output_workspace reported as selected; a selection that changed since that read is refused."

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 / version_id / description

Previous value: -"Version reference from the creative or campaign output workspace."New value: +"Version id to select, from get_campaign_output_workspace."

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, it discloses optimistic concurrency behavior: a stale expected_current_version_id causes refusal so an older choice cannot overwrite a newer one. It also clarifies that selecting the already-selected version is a no-op and that no generation or export occurs.

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 three compact sentences, front-loads the action, and each sentence adds a distinct operational fact: source of IDs, stale-read refusal, and absence of side effects.

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?

For a mutation tool with annotations and an output schema, this covers the key behavioral risks: concurrency refusal, idempotent no-op behavior, and no generation/export side effects. Nothing critical for correct invocation appears to be 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%, so the schema already documents all four parameters in detail. The description reinforces that version_id and expected_current_version_id come from get_campaign_output_workspace and explains the stale-read rationale, but it adds little parameter meaning beyond what the schema already provides.

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 states a specific verb and resource: it makes an existing image version the selected one for a campaign image. It also clearly distinguishes the operation from producing or exporting content by saying it generates and exports nothing.

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?

It explains the required source of the IDs (get_campaign_output_workspace) and the stale-selection refusal condition, which gives clear usage context. It does not explicitly name an alternative tool for other selection workflows, but the when-to-use and failure conditions are well specified.

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.