Skip to main content
Glama

ADS Beast

prepare_campaign_enable

Prepare switching one paused campaign back on. Enabling always waits for a person, whatever the client's write policy. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "campaign_id": "<campaign_id>",
      "reason": "<reason>"
    },
    "name": "prepare_campaign_enable"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
campaign_idYesADS Beast id from list_campaigns, not the platform's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: enabling always waits for human approval regardless of the client's write policy, and the call changes nothing but stores a preview_id with a 15-minute TTL that is single-use. This is exactly the context an agent needs before invoking a non-read-only tool, and it is consistent with readOnlyHint=false and destructiveHint=false.

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; the action is front-loaded, the approval behavior follows, and the mechanics plus next step close it out. There are no filler phrases and every sentence contributes new information.

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 two-parameter prepare tool with no output schema, the description covers the action, the human approval gate, the fact that nothing is mutated yet, the preview_id lifetime and single-use constraint, and the follow-up tool. Nothing needed 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 description coverage is 100%, so both parameters (campaign_id, reason) are already documented in the schema, including the ADS Beast id source and that the reason is shown to the approver. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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: 'Prepare switching one paused campaign back on' / 'Enabling'. It scopes the operation to a single paused campaign and signals the two-step prepare/execute model, which separates it from siblings like prepare_campaign_pause and execute_prepared_change.

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?

The precondition is clear from the text: the campaign must be paused, and this prepares (does not perform) the enable. It also names the follow-up tool, execute_prepared_change. It stops short of explicitly stating when not to use it (for example, that disabling goes through prepare_campaign_pause), so the alternative is implied rather than enumerated.

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.