Skip to main content
Glama

ADS Beast

execute_prepared_change

Destructive

Step 2 of every change: submit one preview made by a prepare_* tool. Only that stored preview runs - this tool takes no other argument, so the change cannot differ from what was shown. A preview works once, for 15 minutes, and is refused when the campaign changed in the meantime. The answer says whether the change now waits for a person's approval in ADS Beast (the default) or is being applied under the client's write policy. This connector cannot approve.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "execute_prepared_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYesThe preview_id returned by a prepare_* tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructive/openWorld annotations, it discloses the single-use preview token, the 15-minute expiry, the stale-campaign refusal, and that the response distinguishes pending human approval from immediate application under write policy. The approval limitation is exactly the kind of context annotations cannot convey.

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?

Front-loads the workflow position, then the constraint, then the return semantics, then the limitation. Four sentences with no filler; each one carries a distinct operational fact.

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?

With no output schema, the description still explains what the response conveys (approval-pending vs. applied). For a single-parameter, high-consequence mutation tool, nothing an agent needs in order to call it safely 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 already 100%, so the schema documents preview_id. The description still adds real meaning: that the ID must originate from a prepare_* tool, that it is consumed on use, and that no other argument exists so the executed change cannot diverge from the preview.

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 ('submit one preview made by a prepare_* tool') and explicitly positions itself as 'Step 2 of every change', which separates it from the prepare_* and get_prepared_change siblings. An agent can identify the operation without opening 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 Guidelines5/5

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

Gives explicit preconditions (must follow a prepare_* call, takes no other argument), lifecycle rules (works once, 15-minute window, refused if the campaign changed), and a hard exclusion ('This connector cannot approve'), routing approval to ADS Beast. When-to-use and when-not-to-use are both covered.

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.