Skip to main content
Glama

ADS Beast

prepare_meta_placement_safety_apply

Prepare removing fraud-prone placements from every ad set of a client's active Meta campaigns. 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": {
      "client_id": "<client_id>",
      "reason": "<reason>"
    },
    "name": "prepare_meta_placement_safety_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
client_idYes
objectiveNoMeta objective, OUTCOME_LEADS by default.
include_bot_audienceNoAlso attach the bot exclusion audience.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The description adds genuinely useful behavior beyond annotations: nothing is mutated, a preview_id is stored, it expires in 15 minutes, and it is single-use. However, 'Changes nothing' sits in mild tension with readOnlyHint=false (a preview record is written), and there is no mention of approval requirements or what an expired preview does — gaps that matter for a write-adjacent prepare step with openWorldHint=true.

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?

Two tight sentences: the action and scope first, then the crucial non-mutating guarantee and next step. No filler, no repetition of the title.

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 prepare tool with no output schema, the description covers the essentials — no side effects, the returned preview_id, its lifetime, single use, and the follow-up tool. Missing only approval-flow and expiry-failure behavior.

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?

With schema coverage at 75%, the schema already documents reason, objective default, and the bot-audience flag. The description adds no per-parameter meaning — it does not say what client_id scope implies or when include_bot_audience should be turned on — so baseline 3 applies.

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 object ('Prepare removing fraud-prone placements'), the exact blast radius ('every ad set of a client's active Meta campaigns'), and explicitly frames the tool as the non-executing half of a two-step flow, which separates it from execute_prepared_change at a glance.

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 second sentence tells the agent exactly what to do next ('execute_prepared_change') and scopes the tool to active campaigns, so the usage context is clear. It stops short of stating when to prefer this over the sibling check tool meta_ads_placement_safety_check or any exclusions for paused campaigns.

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.