Skip to main content
Glama

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

overview_update_ad_statuses

Prepare 1-10 ad configured-status changes in OAuth Safe Mode. Each item needs ad_id, ad_account_id and target_configured_status=ACTIVE|PAUSED. Configured ACTIVE does not prove delivery: a parent may be paused. Review current/new values, then overview_update_confirm after approval

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
connection_contextNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / else / then / properties / category
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / expected
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / else / then / properties / failure_kind
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / responsibility_hint
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / route
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / user_visible
      Added value: +{
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  3. Changed5 schema fields changed
    • addedInput schema / properties / items / items / allOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "properties": {
+          "ad_id": {
+            "not": {
+              "type": "null"
+            }
+          }
+        },
+        "required": [
+          "ad_id"
+        ]
+      },
+      {
+        "properties": {
+          "entity_id": {
+            "not": {
+              "type": "null"
+            }
+          }
+        },
+        "required": [
+          "entity_id"
+        ]
+      }
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "properties": {
+          "target_configured_status": {
+            "not": {
+              "type": "null"
+            }
+          }
+        },
+        "required": [
+          "target_configured_status"
+        ]
+      },
+      {
+        "properties": {
+          "status": {
+            "not": {
+              "type": "null"
+            }
+          }
+        },
+        "required": [
+          "status"
+        ]
+      }
+    ]
+  }
+]
    • addedInput schema / properties / items / items / properties
      Added value: +{
+  "ad_account_id": {
+    "description": "Public ad_account_id from the same ad's read result.",
+    "type": [
+      "string",
+      "number"
+    ]
+  },
+  "ad_id": {
+    "description": "Exact ad_id from the selected read result; no duplicates.",
+    "type": [
+      "string",
+      "number",
+      "null"
+    ]
+  },
+  "entity_id": {
+    "description": "Legacy alias for ad_id; prefer ad_id.",
+    "type": [
+      "string",
+      "number",
+      "null"
+    ]
+  },
+  "status": {
+    "description": "Legacy alias for target_configured_status; if both are set they must agree.",
+    "pattern": "^\\s*(?:[Aa][Cc][Tt][Ii][Vv][Ee]|[Pp][Aa][Uu][Ss][Ee][Dd])\\s*$",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "target_configured_status": {
+    "anyOf": [
+      {
+        "enum": [
+          "ACTIVE",
+          "PAUSED"
+        ],
+        "type": "string"
+      },
+      {
+        "pattern": "^\\s*(?:[Aa][Cc][Tt][Ii][Vv][Ee]|[Pp][Aa][Uu][Ss][Ee][Dd])\\s*$",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    ],
+    "description": "Desired configured state; ACTIVE does not guarantee effective delivery."
+  }
+}
    • addedInput schema / properties / items / items / required
      Added value: +[
+  "ad_account_id"
+]
    • addedInput schema / properties / items / maxItems
      Added value: +10
    • addedInput schema / properties / items / minItems
      Added value: +1
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds real value beyond annotations: it discloses that this is a staging step whose changes only land after confirmation/approval, and warns that 'Configured ACTIVE does not prove delivery: a parent may be paused' — a state-semantics caveat the annotations cannot convey. It does not touch auth requirements or rate limits, and destructiveHint=false plus openWorldHint=true are left largely to the annotations.

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 front-loaded sentences with zero filler: action and scope first, per-item requirements second, the delivery caveat and confirm workflow last. Every clause earns its place.

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?

With an output schema present, return values need no explanation, and the description covers the workflow, item shape, enum, batch bound and a delivery caveat. The only gap is the undocumented connection_context parameter, a minor omission for a moderate-complexity mutation tool.

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?

Top-level schema description coverage is 0%, so the description carries weight: it enumerates the required item fields (ad_id, ad_account_id, target_configured_status) and inlines the enum (ACTIVE|PAUSED). It does not explain connection_context or the legacy alias fields (status/entity_id), leaving some of the schema-silent surface undocumented.

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?

States a specific verb and resource ('Prepare 1-10 ad configured-status changes') plus the operating mode ('OAuth Safe Mode'), and the batch count (1-10) implicitly separates it from the single-ad siblings like ads_prepare_status_change. An agent can tell what this does and how it differs from singular status-change tools without opening the schema.

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?

Names the next step explicitly ('then overview_update_confirm after approval') and gives the condition (after approval), providing a clear prepare-then-confirm workflow. It does not state when-not-to-use or name ineligible cases, so it falls short of full when/when-not/alternatives coverage.

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

All AdsAgent — Meta Ads MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources