Skip to main content
Glama

ADS Beast

prepare_meta_audiences_create

Prepare website custom audiences and lookalikes in a client's Meta account. 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_audiences_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
client_idYes
audience_typesNoAudience types to create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is partly covered; the description adds the important nuance that nothing in the Meta account is changed and that the tool only persists a short-lived preview_id. There is mild tension between 'Changes nothing' and readOnlyHint=false, since it does write a preview record, but this is clarifying rather than contradictory. It does not explain what the preview shows or what approval is required.

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 short sentences, front-loaded with the action and followed by the safety and workflow constraint. Every clause carries information: scope, no-change guarantee, TTL, single use, and the next tool.

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 3-parameter staging tool with annotations and no output schema, the description covers purpose, side-effect profile, preview lifetime, and the required follow-up call. Missing details are secondary: what the preview contains, whether an approver step gates execution, and what the default audience set produces.

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 67% schema description coverage, the schema already documents reason and audience_types, so the baseline of 3 applies. The description's mention of 'website custom audiences and lookalikes' loosely maps to the website_* and lal_* enum values, but client_id is undocumented in both places and nothing is said about defaults or how the reason is consumed by the approver.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: prepare website custom audiences and lookalikes in a client's Meta account. The scope is unambiguous, but the sibling prepare_meta_audience_create is nearly identical in name and is not addressed, so an agent cannot tell the two apart from the description alone.

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?

Clearly establishes the two-step workflow by naming execute_prepared_change as the follow-up and stating the preview_id is single use and expires in 15 minutes. It does not say when to prefer this over the similarly named prepare_meta_audience_create or prepare_meta_ad_set_create, which is the main gap.

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.