Skip to main content
Glama

Create Ad

meta_create_ad

Create a new ad in a Meta ad set by using an existing creative ID and setting the status to active or paused.

Instructions

Creates a new ad within an ad set.

Args:

  • ad_account_id (string): Ad account ID

  • adset_id (string): Parent ad set ID

  • name (string): Ad name

  • creative_id (string): Ad creative ID (from meta_list_ad_creatives or meta_create_ad_creative)

  • status (string): ACTIVE or PAUSED (default PAUSED)

Returns the new ad ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_account_idYes
adset_idYes
nameYes
creative_idYesAd creative ID
statusNoPAUSED
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior2/5

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

Annotations already indicate a write operation (readOnlyHint=false, destructiveHint=false). The description only adds that it returns the new ad ID, lacking details on side effects, permissions, 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?

The description is brief, uses a clear bullet-like structure, and every sentence adds value without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with no output schema, the description covers essential parameters and return value, but lacks details on prerequisites, error handling, or whether creation is immediate.

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?

The description explains the purpose of five parameters (ad_account_id, adset_id, name, creative_id, status) beyond the schema, referencing sibling tools for creative_id. However, it omits the response_format parameter entirely.

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 clearly states 'Creates a new ad within an ad set' with a specific verb and resource, distinguishing it from other creation tools like meta_create_ad_creative or meta_create_adset.

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?

The description hints at using creative_id from meta_list_ad_creatives or meta_create_ad_creative, but does not explicitly state when to use this tool versus alternatives like update or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oliverames/meta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server