Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ad_sets_pause

Pause an ad set to stop its ads from serving. Ads under it halt immediately, even if active, while sibling ad sets remain unaffected. Reversible via enable.

Instructions

Pauses a single ad set by setting its status to PAUSED. Ads under this ad set stop serving while it is PAUSED, even if their own status is ACTIVE. Lightweight, reversible via rollback_apply or meta_ads_ad_sets_enable. Returns the ad_set_id and new status. Does not affect sibling ad sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
ad_set_idYesAd set ID to pause.
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.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral trait: setting status to PAUSED stops ads under the ad set even if their own status is ACTIVE. It also states the action is lightweight, reversible, and does not affect sibling ad sets. It does not mention permission requirements or whether the change is immediate, but the core behavioral disclosure is strong.

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 three sentences, front-loaded with the core action and effect, then reversibility and scope. Every sentence earns its place: action, consequence, reversibility, return value, and non-effect on siblings. No fluff.

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

Completeness4/5

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

For a single-resource mutation tool with no output schema and no annotations, the description covers the action, effect, reversibility, and scope. It does not describe the exact return format beyond 'ad_set_id and new status', but that is sufficient for an agent to know what to expect. It could mention permission requirements or failure modes, but the core context is complete.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds value by explaining the effect of the ad_set_id parameter (the ad set to pause) and the reversibility context, but it does not add much beyond the schema for reason or account_id. Baseline 3 is elevated to 4 because the description clarifies the primary parameter's role and the overall operation semantics.

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 ('Pauses'), a specific resource ('a single ad set'), and the mechanism ('by setting its status to PAUSED'). It also distinguishes itself from sibling tools by noting it affects only the target ad set and not sibling ad sets, and by naming the reversible alternatives (rollback_apply or meta_ads_ad_sets_enable).

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?

The description explicitly says when to use this tool (to pause a single ad set) and what happens as a result (ads under it stop serving even if ACTIVE). It also names the alternatives for reversing the action (rollback_apply or meta_ads_ad_sets_enable), giving clear context for when to use those instead. It does not explicitly list exclusions, but the scope is precise enough.

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