StealAds

Update creative copy

update_copy

Idempotent

Saves primary text and/or call-to-action wording supplied by the user for a finished image ad, as a new entry in its copy history. For exact wording the user dictates; revise_copy asks StealAds to write a proposal instead. The headline and the image are not changed, nothing is generated and no credits are spent. At least one of primary_text and cta is needed.

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": {
      "generation_job_id": "<generation_job_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "update_copy"
  }
}

Input Schema

Name	Required	Description
`cta`	No	New call-to-action text exactly as it is to be saved, up to 100 characters.
`primary_text`	No	New main ad text exactly as it is to be saved, up to 5,000 characters.
`idempotency_key`	Yes	Caller-chosen unique value for this change (1 to 128 letters, digits, hyphens or underscores), not a value from a preview. A repeat with the same value returns the original result.
`generation_job_id`	Yes	Finished-image reference of a single ad: _references.generation_job_id on a list_generation_jobs row. Not the job_id that get_ad_status takes.

Output Schema

Name	Required	Description
`status`	No	Current progress or delivery state.
`version_id`	No	version id value in this response.
`cost_credits`	No	Credits quoted or charged by this operation.
`refund_credits`	No	refund credits value in this response.
`original_cost_credits`	No	original cost credits value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 10, 2026

changedInput schema / properties / cta / description

Previous value: -"Call to action text."New value: +"New call-to-action text exactly as it is to be saved, up to 100 characters."

changedInput schema / properties / generation_job_id / description

Previous value: -"Generated image reference from list_generation_jobs or get_campaign_outputs."New value: +"Finished-image reference of a single ad: _references.generation_job_id on a list_generation_jobs row. Not the job_id that get_ad_status takes."

changedInput schema / properties / idempotency_key / description

Previous value: -"Confirmation key from the cost preview; valid for 15 minutes."New value: +"Caller-chosen unique value for this change (1 to 128 letters, digits, hyphens or underscores), not a value from a preview. A repeat with the same value returns the original result."

changedInput schema / properties / primary_text / description

Previous value: -"Main ad copy."New value: +"New main ad text exactly as it is to be saved, up to 5,000 characters."

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare a non-destructive, idempotent write; the description adds substantive context beyond them — the write is append-only to a copy history, the headline and image are untouched, nothing is generated and no credits are spent. That directly answers the main agent worry for a write tool. It stops short of saying whether the new entry can be reverted via undo_copy_revision.

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?

Four short sentences, front-loaded with what is saved, then the sibling routing, then side effects, then the input constraint. Every sentence carries distinct decision-relevant information with no filler.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, alternative routing, side effects and the key input constraint. The only omission is how a saved entry can later be undone or applied, which a cautious agent might want for a mutation tool.

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 each parameter's meaning and format is already fully documented. The description adds one real constraint beyond the schema — that at least one of primary_text and cta must be supplied, since neither is formally required — but adds no further semantic detail. Baseline 3 applies with that small lift.

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?

States a specific verb and resource ('Saves primary text and/or call-to-action wording ... as a new entry in its copy history') and explicitly contrasts itself with revise_copy, so an agent can distinguish it from the most likely sibling without opening either schema.

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?

Gives a clear selection rule: use this when the user dictates exact wording, use revise_copy when StealAds should generate a proposal. That is genuine when-to-use vs alternative guidance. It does not mention revert paths (undo/discard of copy history entries), which is the main remaining gap.

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.