StealAds

Revise creative copy

revise_copy

Idempotent

Asks StealAds to rewrite the copy of a finished image ad as a proposal; the current copy stays in place until the proposal is applied. Two steps: without confirm it returns a cost preview (idempotency_key, max_credits) and changes nothing; the same call with confirm: true and those two values starts the rewrite. get_creative_workspace then shows the proposal as pending, and apply_copy_revision or discard_copy_revision settles it. A delivered proposal is charged even when discarded; update_copy saves wording the user supplies without a charge.

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>",
      "mode": "<mode>"
    },
    "name": "revise_copy"
  }
}

Input Schema

Name	Required	Description
`mode`	Yes	change_words rewords the current message; new_angle writes the copy around a different angle.
`note`	No	Optional guidance for the rewrite, up to 1,000 characters. The preview key is tied to this exact note.
`confirm`	No	true starts the rewrite shown in the cost preview; absent or false returns the preview and spends nothing.
`max_credits`	No	max_credits from the cost preview, sent with confirm: true as the approved credit ceiling.
`idempotency_key`	No	idempotency_key from the cost preview, needed with confirm: true and valid for 15 minutes.
`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.
`billing_url`	No	billing url value in this response.
`max_credits`	No	Explicit credit ceiling to echo after the user approves this quote.
`next_action`	No	Suggested operation to continue or recover from this state.
`cost_credits`	No	Credits quoted or charged by this operation.
`what_happens`	No	Plain explanation of the proposed work, confirmation steps and quote expiry.
`enough_credits`	No	enough credits value in this response.
`refund_credits`	No	refund credits value in this response.
`balance_credits`	No	balance credits value in this response.
`idempotency_key`	No	Key binding confirmation to this preview and preventing duplicate work.
`confirmation_required`	No	True for a cost preview awaiting explicit approval.
`original_cost_credits`	No	original cost credits value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026

changedInput schema / properties / confirm / description

Previous value: -"Whether the user has approved the displayed preview; defaults to false."New value: +"true starts the rewrite shown in the cost preview; absent or false returns the preview and spends nothing."

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: +"idempotency_key from the cost preview, needed with confirm: true and valid for 15 minutes."

changedInput schema / properties / max_credits / description

Previous value: -"Explicit credit ceiling approved from the preview."New value: +"max_credits from the cost preview, sent with confirm: true as the approved credit ceiling."

changedInput schema / properties / mode / description

Previous value: -"Kind of copy revision to propose."New value: +"change_words rewords the current message; new_angle writes the copy around a different angle."

changedInput schema / properties / note / description

Previous value: -"Optional note about the source or change."New value: +"Optional guidance for the rewrite, up to 1,000 characters. The preview key is tied to this exact note."

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare this a non-read-only, idempotent, non-destructive, open-world write; the description adds the behavior that matters: nothing changes until the proposal is applied, the preview spends nothing, a delivered proposal is charged even if discarded, and the idempotency key expires after 15 minutes. That billing and reversibility detail is exactly the context annotations cannot express.

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?

Front-loaded with the core action, then the two-step mechanics, then the settlement and charging caveats. Dense but essentially waste-free; the single long sentence about get_creative_workspace/apply/discard packs three routing facts together, which is slightly heavy but still parseable.

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?

An output schema exists, so return shape needn't be explained, and the description still covers the non-obvious return fields an agent must feed back (idempotency_key, max_credits) and where to see the result afterward. For a charged, multi-step mutation, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 3 is the baseline, but the description adds cross-parameter meaning the schema can't: confirm is the switch between the free preview and the charged rewrite, and idempotency_key and max_credits must be the exact values from that preview. The note-to-key binding is echoed from the schema rather than newly explained, which keeps this just shy of a 5.

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?

"Asks StealAds to rewrite the copy of a finished image ad as a proposal" gives a specific verb (rewrite), resource (ad copy), and output form (proposal, not a direct edit). It explicitly separates itself from update_copy (user-supplied wording, no charge) and from apply_copy_revision/discard_copy_revision (which settle the proposal), so an agent can route correctly without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives an explicit two-step protocol: call without confirm for a preview, then repeat with confirm: true plus the returned idempotency_key and max_credits. It also states the alternative path (update_copy when the user supplies the wording) and the follow-up tools (get_creative_workspace to see it pending, apply/discard to settle), covering when-to-use and when-to-use-something-else.

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.