Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ads_create

Create a new ad in an existing ad set by binding it to a pre-existing creative. Returns the new ad ID with default status PAUSED.

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.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well. It discloses that the operation is mutating and not automatically reversible, recommends recording before-state via mureo_state_action_log_append, states the default initial status is PAUSED, and requires the creative to already exist.

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 four sentences with no filler. It front-loads the core purpose and return value, then adds the rollback caveat, default status, and prerequisite. Every sentence adds distinct value.

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 mutation tool with no annotations and no output schema, the description is complete enough: it explains what happens, what it returns, the default status, the mutation risk, and the prerequisite. Combined with the thorough schema, an agent has everything needed to invoke it correctly.

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 description coverage is 100%, so the schema already documents all six parameters. The description adds contextual meaning around creative_id ('binding it to a pre-existing creative' and 'must already exist') but mostly restates what the schema already provides, fitting the baseline.

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 states a specific verb and resource: creates a new ad inside an existing ad set, binding it to a pre-existing creative. It also names the return value (new ad id), which clarifies scope and distinguishes this from ad update, pause, and enable siblings.

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?

It gives clear context: the creative must already exist and names the exact tools to create one (meta_ads_creatives_create and sibling constructors like meta_ads_creatives_create_carousel). It does not explicitly contrast with meta_ads_ads_update or the pause/enable tools, but the prerequisite and mutation framing make the intended use clear.

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

Deploy Server

Other Tools