Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

create

Create a paused Meta campaign, ad set, creative, or ad in your configured ad account, requiring explicit user confirmation before any change is applied.

Instructions

Create a campaign, ad set, creative, or ad in the configured ad account. Campaigns, ad sets, and ads are always created PAUSED. Requires explicit user confirmation.

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": {
      "object_type": "<object_type>",
      "params": "<params>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "create"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYesMarketing API fields for the object. Nested objects and arrays are JSON-encoded by the server. Budgets are in the minor unit of the account currency.
object_typeYes
change_summaryYesConcise exact change the user approved in the current request, with budget and status.
user_confirmedYesMust be true only after explicit action-time user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world mutation. The description adds two traits the annotations do not carry: new campaigns, ad sets, and ads are always created PAUSED, and an explicit user confirmation is required. That is meaningful behavioral context for a write tool; it stops short of describing failure modes or rate limits.

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, front-loaded with the action and resource, then the safety-relevant default state, then the confirmation requirement. No filler or repetition of structured fields.

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 nested-parameter mutation with no output schema, the description covers what it creates, where, in what state, and the confirmation gate. The main remaining gap is that, absent an output schema, it never indicates what the call returns (e.g. created object IDs), which an agent needs to chain follow-up calls.

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 75% and the schema already documents params, change_summary, and user_confirmed, including the JSON-encoding and minor-unit conventions. The description contributes only the account scoping and adds nothing about object_type or the required change_summary content, so the schema is doing the heavy lifting.

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?

The description gives a specific verb ('Create') plus the resource and enumerates the four creatable object types (campaign, ad set, creative, ad), scoped to 'the configured ad account'. This is enough to distinguish it from siblings such as update, copy, and set_status without opening any schema.

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?

It states a hard precondition ('Requires explicit user confirmation'), which is real when-to-use guidance, but it never routes the agent between this tool and alternatives like copy or update, nor does it say what to do if the object already exists. Usage is implied rather than fully framed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.