Skip to main content
Glama

ADS Beast

prepare_meta_ad_set_create

Prepare a new ad set inside an existing Meta campaign. The ad set is created PAUSED. daily_budget is in whole units of the account currency (20 means 20.00); the preview shows the figure Meta receives. 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>",
      "name": "<name>",
      "daily_budget": "<daily_budget>",
      "targeting": "<targeting>",
      "reason": "<reason>"
    },
    "name": "prepare_meta_ad_set_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAd set name.
reasonYesWhy, with numbers (shown to the approver).
targetingYesMeta targeting spec: geo_locations, age_min, age_max, genders, locales, interests or flexible_spec, custom audiences, plus audience_rationale.
campaign_idYesADS Beast id from list_campaigns, not the platform's.
daily_budgetYesDaily budget in the ad account's currency, whole units.
optimization_goalNoWhat Meta optimises the ad set for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the ad set lands PAUSED, nothing in the account changes, and the stored preview_id is single-use with a 15-minute TTL. The "Changes nothing" wording sits slightly against readOnlyHint=false, but the description resolves it by explaining that what is stored is a preview handle, so this reads as clarification rather than contradiction.

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?

Four short sentences, front-loaded with what the tool does, then the two details an agent is most likely to get wrong (budget units and the preview lifecycle). No filler.

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?

There is no output schema, and the description still explains what comes back (a preview_id with its constraints) and what the preview displays. The nested targeting spec is left entirely to the schema, which documents it adequately, so only minor gaps remain.

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 100%, so the baseline is 3; the description earns more by spelling out the daily_budget unit convention with a worked example (20 means 20.00) and by noting the preview echoes the figure Meta will receive, which is meaning the schema alone doesn't convey.

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 a new ad set inside an existing Meta campaign") and pins the scope: it prepares a preview rather than creating anything live, which distinguishes it from execute_prepared_change and prepare_ad_create.

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?

Explicitly names the follow-up step ("then execute_prepared_change") so the two-phase flow is unambiguous. It does not explicitly say when to prefer this over prepare_ad_create or other prepare_* siblings, but the campaign-ad-set scope is clear enough to route correctly.

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.