Skip to main content
Glama

Discard a copy revision

discard_copy_revision
DestructiveIdempotent

Rejects a delivered pending copy proposal from revise_copy; the ad’s current copy stays as it is. Takes the pending version_id that get_creative_workspace reports. The charge for the delivered proposal is kept.

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": "discard_copy_revision"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "https://json-schema.org/draft/2020-12/schema",
      -  "additionalProperties": false,
      -  "properties": {
      -    "cost_credits": {
      -      "anyOf": [
      -        {
      -          "description": "Credits quoted or charged by this operation.",
      -          "type": "number"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "Credits quoted or charged by this operation."
      -    },
      -    "original_cost_credits": {
      -      "anyOf": [
      -        {
      -          "description": "original cost credits value in this response.",
      -          "type": "number"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "original cost credits value in this response."
      -    },
      -    "refund_credits": {
      -      "anyOf": [
      -        {
      -          "description": "refund credits value in this response.",
      -          "type": "number"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "refund credits value in this response."
      -    },
      -    "status": {
      -      "anyOf": [
      -        {
      -          "default": "processing",
      -          "description": "Current progress or delivery state.",
      -          "enum": [
      -            "queued",
      -            "running",
      -            "processing",
      -            "completed",
      -            "complete",
      -            "failed",
      -            "cancelled",
      -            "pending",
      -            "ready",
      -            "started",
      -            "already_started",
      -            "already_done",
      -            "in_progress",
      -            "active",
      -            "paused",
      -            "draft",
      -            "kept",
      -            "discarded",
      -            "delivered",
      -            "expired",
      -            "reserved",
      -            "settled",
      -            "released",
      -            "held",
      -            "consumed",
      -            "generating",
      -            "unknown"
      -          ],
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "Current progress or delivery state."
      -    },
      -    "version_id": {
      -      "anyOf": [
      -        {
      -          "description": "version id value in this response.",
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ],
      -      "description": "version id value in this response."
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  2. 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)."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (destructive=true, idempotent=true), the description adds two genuinely useful facts: the live ad copy is untouched, and the charge for the delivered proposal is still incurred. It does not say whether the discarded proposal can be recovered or re-proposed, which matters for a destructive action.

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, each earning its place: action and outcome first, parameter source second, billing consequence last. No filler or redundancy.

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?

For a single-parameter destructive tool with no output schema, it covers the action, the state outcome, the parameter source, and the cost side effect. The only gap is recoverability/retry guidance after discarding, which the annotations' idempotent hint partially mitigates.

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 schema already states version_id comes from get_creative_workspace's pending.version_id, which the description largely restates. With the schema doing the heavy lifting, this sits at the baseline of 3; the only added nuance is emphasizing the value must be the *pending* one.

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?

Names a specific verb and resource ('Rejects a delivered pending copy proposal from revise_copy') and immediately states the resulting state of the ad ('the ad's current copy stays as it is'). This clearly separates it from revise_copy, apply_copy_revision, and undo_copy_revision without needing the 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 gives a clear trigger condition: use it on a *pending* proposal produced by revise_copy, with the version_id obtained from get_creative_workspace. It does not explicitly contrast with apply_copy_revision or undo_copy_revision, so the agent must infer that those handle approving or reverting applied changes rather than discarding pending ones.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.