Skip to main content
Glama

meta_ads_ads_create

Creates a new ad in an existing ad set by linking a pre-existing creative. Returns the new ad ID.

Instructions

Creates a new ad inside an existing ad set, binding it to a pre-existing creative. Returns the new ad id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. 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
nameYesAd name visible in Ads Manager.
statusNoInitial status. Default PAUSED; only ACTIVE after operator sign-off.
ad_set_idYesParent ad set ID. Must exist and not be DELETED.
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.
creative_idYesExisting AdCreative ID to bind to this ad. Obtain from meta_ads_creatives_list / create.
Behavior5/5

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

Despite no annotations, the description fully discloses mutating behavior, irreversibility, default initial status PAUSED, and the necessity of pre-existing creative. Even recommends a rollback logging tool, which goes beyond basic transparency.

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?

Every sentence adds value. The description is front-loaded with the main action, then covers mutability, status, and prerequisite. No wasted words; efficient and clear.

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?

Complete for a creation tool: explains inputs, prerequisites, mutation behavior, default status, rollback suggestion, and return value (new ad id). No output schema exists, but the description covers what the agent needs to know.

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 context for creative_id (must exist from list/create) and status (only ACTIVE after operator sign-off), enhancing understanding beyond the schema. However, other parameters like account_id and ad_set_id are not enriched beyond schema.

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 the verb 'creates', resource 'new ad inside an existing ad set', and binding to a pre-existing creative. Returns the new ad id. Distinguishes from sibling tools like meta_ads_creatives_create or meta_ads_ads_update.

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

Usage Guidelines5/5

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

Explicitly states that the creative must already exist and refers to sibling tools (meta_ads_creatives_create) for creating creatives. Also warns about mutating irreversibility and suggests using mureo_state_action_log_append for rollback. Provides clear prerequisites and default status 'PAUSED'.

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