Skip to main content
Glama
Sign In

StealAds

by ai.stealads
OverviewDiscussionsAdmin

Apply a copy revision

apply_copy_revision
Idempotent

Accepts a delivered pending copy proposal from revise_copy and makes it the ad’s current copy. Takes the pending version_id that get_creative_workspace reports. No further charge; undo_copy_revision can bring the earlier copy back.

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": {
      "version_id": "<version_id>"
    },
    "name": "apply_copy_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
version_idYesversion_id of the pending revision, from get_creative_workspace (pending.version_id).

Output Schema

NameRequiredDescriptionDefault
statusNoCurrent progress or delivery state.
version_idNoversion id value in this response.
cost_creditsNoCredits quoted or charged by this operation.
refund_creditsNorefund credits value in this response.
original_cost_creditsNooriginal cost credits value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version_id / description
      Previous value: -"Version reference from the creative or campaign output workspace."New value: +"version_id of the pending revision, from get_creative_workspace (pending.version_id)."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it discloses the billing trait ('No further charge') and the reversibility path (undo_copy_revision restores the earlier copy), which the hints alone don't convey. It implies the prior current copy is replaced but doesn't spell out exactly what state is lost if undo is not used, which slightly limits completeness for a mutation.

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?

Three short sentences, front-loaded with the action, then the input source, then cost and reversal. Every sentence earns its place with zero padding.

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 one-parameter mutation with a rich annotation set and an output schema, the description covers what changes, where the input comes from, cost, and how to reverse it. 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.

Parameters3/5

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

Schema coverage is 100% and the single parameter is already documented with its source path, so the schema carries the load. The description reinforces the workflow provenance — the version_id comes from the pending proposal created by revise_copy — but adds no format or validation detail beyond that.

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 names a specific verb and resource ('makes it the ad's current copy') and explicitly ties the tool to its producer, revise_copy, and its inverse, undo_copy_revision. An agent can distinguish it from revise_copy and discard_copy_revision without opening any 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?

It clearly states the precondition (a delivered pending proposal must exist from revise_copy) and the exact input source (the pending version_id get_creative_workspace reports). It also names undo_copy_revision as the reversal path, but it never explicitly says when not to apply a revision (e.g., use discard_copy_revision to abandon a proposal instead), so it stops short of full when/when-not coverage.

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

All StealAds toolsInspect
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.

Resources