Skip to main content
Glama

ADS Beast

prepare_meta_audience_create

Prepare one custom audience (customer list, website pixel, app or offline) or one lookalike 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>",
      "audience_type": "<audience_type>",
      "name": "<name>",
      "reason": "<reason>"
    },
    "name": "prepare_meta_audience_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAudience name in the Meta account.
ratioNoFor lookalike: size 0.01-0.20 (1-20% of the country).
reasonYesWhy, with numbers (shown to the approver).
countryNoFor lookalike: country code, e.g. PL.
subtypeNoFor custom: CUSTOM, WEBSITE, APP or OFFLINE_CONVERSION.
pixel_idNoFor WEBSITE: Meta pixel id.
client_idYes
audience_typeYescustom or lookalike.
retention_daysNoFor WEBSITE: days a visitor stays in the audience.
source_audience_idNoFor lookalike: Meta id of the source custom audience.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, and the description resolves that ambiguity by explaining nothing is changed in the account and only a short-lived, single-use preview_id is written. The 15-minute expiry and single-use constraint are behavioral facts not present in the annotations or schema. It does not describe the response shape (e.g., whether a preview summary is returned alongside the id).

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 what is created and followed immediately by the key safety fact and next step. No filler and no repetition of schema content.

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 10-parameter preparation tool with no output schema, the description conveys the no-op safety model, the preview lifetime, and the required follow-up call. Remaining gaps (return format of the preview, what the approver sees) are minor given the rich schema descriptions and existing annotations.

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 90%, so nearly every parameter is already described at field level, including the custom/lookalike conditionals (subtype, pixel_id, retention_days, source_audience_id, ratio, country). The description only restates the audience categories and adds no format or interaction detail beyond the schema, so baseline 3 applies.

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 (Prepare) and resource (one custom audience or one lookalike) with the four custom subtypes enumerated in parentheses, and scopes it to a client's Meta account. It is distinguishable from the plural sibling prepare_meta_audiences_create by the word "one," though that distinction is implicit rather than called out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Gives clear workflow guidance: this stores a preview_id (15 min, single use) to show and then execute_prepared_change, which tells the agent this is step one of a two-step flow. It does not say when to pick this over the batch sibling prepare_meta_audiences_create, nor what happens if the preview expires unreviewed.

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.