Skip to main content
Glama
Sign In

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

overview_get_live_configs

Read current Meta status, budget, bid, and other settings for up to 50 known campaigns, ad sets, or ads in your authorized accounts. With mutation_ref, also save verification of that operation in AdsAgent using its original writer. Does not change ads or delivery

Input Schema

NameRequiredDescriptionDefault
entitiesYes
mutation_refNo
response_modeNocompact
metadata_contract_versionNo

Output Schema

NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / connection_context
      Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}
  2. Changed6 schema fields changed
    • addedOutput schema / then / properties / category
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / expected
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / then / properties / failure_kind
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / responsibility_hint
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / route
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / user_visible
      Added value: +{
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  4. Changed2 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
+  "s0": {
+    "properties": {
+      "can_report_stored_total": {
+        "type": "boolean"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "zero_proven": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "can_report_stored_total",
+      "zero_proven",
+      "reason"
+    ],
+    "type": "object"
+  }
+}
    • addedOutput schema / else / properties / read_evidence
      Added value: +{
+  "description": "Proofs apply independently to returned metrics and scope as stored/observed. A new read_ref is a call identifier, never a source watermark. False or missing proof means unknown, not zero. Fingerprints correlate requests/results in audits; they are not authorization or pagination tokens.",
+  "properties": {
+    "artifact_returned": {
+      "type": "boolean"
+    },
+    "configuration": {
+      "properties": {
+        "account_inventory_enumerated": {
+          "const": false
+        },
+        "all_campaigns_paused_proven": {
+          "const": false
+        },
+        "requested_ids_complete": {
+          "type": "boolean"
+        },
+        "scope": {
+          "const": "requested_entity_ids_only"
+        }
+      },
+      "type": "object"
+    },
+    "mmp": {
+      "properties": {
+        "can_report_scoped_totals": {
+          "type": "boolean"
+        },
+        "provider_cache_max_age_seconds": {
+          "const": 90
+        },
+        "reason": {
+          "type": "string"
+        },
+        "scope": {
+          "const": "linked_apps_queried_channels_and_windows"
+        },
+        "source_observed_at": {
+          "type": "null"
+        }
+      },
+      "type": "object"
+    },
+    "read_ref": {
+      "pattern": "^read_[0-9a-f]{32}$",
+      "type": "string"
+    },
+    "request_fingerprint": {
+      "type": "string"
+    },
+    "result_fingerprint": {
+      "type": "string"
+    },
+    "scopes": {
+      "items": {
+        "properties": {
+          "all_campaigns_paused_proven": {
+            "const": false
+          },
+          "funnel": {
+            "additionalProperties": {
+              "$ref": "#/$defs/s0"
+            },
+            "maxProperties": 32,
+            "type": "object"
+          },
+          "index": {
+            "type": "integer"
+          },
+          "inventory_anchor": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "inventory_coverage": {
+            "type": "string"
+          },
+          "inventory_source_observed_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "metrics": {
+            "additionalProperties": {
+              "$ref": "#/$defs/s0"
+            },
+            "type": "object"
+          },
+          "metrics_source_observed_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "range_complete": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "scope": {
+            "const": "stored_query"
+          }
+        },
+        "type": "object"
+      },
+      "maxItems": 10,
+      "type": "array"
+    }
+  },
+  "required": [
+    "read_ref",
+    "request_fingerprint",
+    "result_fingerprint"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The description reconciles the non-obvious readOnlyHint=false annotation by disclosing that with mutation_ref it writes a verification record into AdsAgent under the original writer, and adds the reassuring scope "Does not change ads or delivery" on top of destructiveHint=false. It stops short of stating auth requirements, whether the mutation_ref must correspond to a previously executed operation, or what idempotency applies if it doesn't.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the primary read purpose and followed by the conditional side effect and the non-mutation guarantee. Only "and other settings" is wasted vagueness; everything else earns its place.

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

Completeness3/5

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

An output schema exists, so return-shape explanation is rightly omitted, and the safety profile is covered. For a 4-parameter tool with a conditional write path, though, the description never explains response_mode's effect on payload size or the verification-write contract, which an agent needs to call 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 0%, so the description must carry all param meaning; it does partially — it explains that entities are known campaign/adset/ad IDs from authorized accounts with a 50 cap, and it explains what mutation_ref triggers. It says nothing about response_mode (compact vs standard) or metadata_contract_version, so half the parameters remain opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — reading live Meta status, budget, bid and settings for campaigns, ad sets or ads — plus a hard scope limit of 50 entities, so the agent knows this returns current configuration rather than performance data. It does not explicitly name the sibling it supersedes among the overview/insights read tools (console_query_overview, insights_query_overview), so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

"For up to 50 known campaigns, ad sets, or ads" implies the prerequisite (the agent must already hold entity IDs, e.g. from entities_lookup_by_name), and the mutation_ref clause implies a post-mutation verification flow. But there is no explicit when-to-use/when-not guidance and no alternative tool named, leaving routing to inference.

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