Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ads_update

Update an existing Meta ad's fields such as name or status, returning the updated ad. If the creative needs to change, create a replacement ad instead.

Instructions

Updates fields on an existing ad. Partial update. Returns the updated ad. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. The ad's creative cannot be swapped via this call — creative changes require creating a replacement ad with a new creative_id and pausing the old one. For status-only transitions use meta_ads_ads_pause / meta_ads_ads_enable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew ad name.
ad_idYesAd ID to update.
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.
statusNoNew ad status. Prefer meta_ads_ads_pause / meta_ads_ads_enable for ACTIVE ↔ PAUSED.
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.

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
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and uses it well: it labels the operation Mutating, warns it is not automatically reversible, and instructs the agent to record before-state with mureo_state_action_log_append. It also discloses that the call returns the updated ad. It does not discuss auth requirements or potential delivery side effects, but the core mutation and rollback behavior is transparent.

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?

Four short sentences, no filler, with the primary action and return value front-loaded before caveats and alternatives. Every sentence adds distinct value: operation, mutation warning, creative constraint, and sibling routing.

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 mutating, partially reversible tool with no output schema and no annotations, the description covers the operation, return value, reversibility/rollback, a key field exclusion (creative), and the correct alternative tools. An agent has enough context to decide whether to call this tool and how to plan around its limitations.

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 five parameters and the account_id format. The description adds useful contextual guidance about status and creative but does not add parameter-level meaning beyond the schema, matching the baseline of 3.

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?

Opens with a concrete verb and resource—'Updates fields on an existing ad'—and clarifies partial update semantics. It also names what the tool cannot do (creative swap) and points to pause/enable siblings, making it easy to distinguish from related meta_ads tools.

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?

Gives explicit when-not-to-use guidance for status-only transitions, naming meta_ads_ads_pause / meta_ads_ads_enable as the correct alternatives. It also specifies the workflow for creative changes (replacement ad + pausing old one), leaving no ambiguity about which tool handles that case.

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