Skip to main content
Glama

meta_ads_ads_create

Creates an ad in an existing ad set by binding a pre-existing creative. Returns the new ad ID. Default status is PAUSED.

Instructions

Creates a new ad inside an existing ad set, binding it to a pre-existing creative. Returns the new ad id. Mutating, reversible via rollback_apply. Default initial status is PAUSED. The creative must already exist — use meta_ads_creatives_create (or sibling constructors like meta_ads_creatives_create_carousel) to produce a creative_id before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
ad_set_idYesParent ad set ID. Must exist and not be DELETED.
nameYesAd name visible in Ads Manager.
creative_idYesExisting AdCreative ID to bind to this ad. Obtain from meta_ads_creatives_list / create.
statusNoInitial status. Default PAUSED; only ACTIVE after operator sign-off.
Behavior4/5

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

Since no annotations are provided, the description carries full burden. It discloses the mutating nature, reversibility, and default status (PAUSED). It does not mention auth needs or rate limits, but the key behavioral traits are covered adequately for a typical tool.

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 concise sentences, each earning its place. The first sentence states action and result, second adds behavioral traits, third gives prerequisite and sibling reference. No wasted words.

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

Completeness5/5

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

For a simple creation tool with no output schema, the description covers the return value, prerequisites, dependencies, and sibling tools. It is complete enough for an agent to use correctly without additional context.

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 baseline is 3. The description adds vital context: creative_id must exist and how to obtain it, account_id is optional with fallback, name is visible in Ads Manager, and status default is PAUSED. This goes beyond schema descriptions.

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?

Clearly states it creates an ad inside an ad set, binding to a creative, and returns the ID. The verb 'creates' and specific resource 'ad inside an ad set' make the purpose unambiguous. Distinguishes itself from creative creation tools by mentioning the prerequisite and where to get creative_id.

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?

Provides explicit prerequisite: creative must exist, and directs to meta_ads_creatives_create and similar siblings. Mentions reversibility via rollback_apply, but does not explicitly state when not to use this tool (e.g., if ad already exists). Still, the guidance is clear and helpful.

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/logly/mureo'

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