Skip to main content
Glama

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

assets_list_pages

List Facebook Pages this workspace can advertise with, with health. Cache miss/authorized refresh may queue private work; filter then paginate; assets_lookup_business_links

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
searchNo
refreshNo
fb_user_labelNo
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 / 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"
+}
  2. Changed1 schema field changed
    • addedOutput schema / else / properties / items / items / properties / whatsapp_connected
      Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  4. Changed7 schema fields changed
    • addedOutput schema / $defs
      Added value: +{
+  "s0": {
+    "properties": {
+      "count": {
+        "type": "integer"
+      },
+      "has_more": {
+        "type": "boolean"
+      },
+      "items": {
+        "items": {
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": [
+                "null",
+                "string"
+              ]
+            }
+          },
+          "required": [
+            "id"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "count",
+      "items",
+      "has_more"
+    ],
+    "type": "object"
+  },
+  "s3": {
+    "properties": {
+      "status": {
+        "enum": [
+          "requires_validation",
+          "awaiting_assets",
+          "blocked"
+        ],
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "status",
+      "summary"
+    ],
+    "type": "object"
+  }
+}
    • addedOutput schema / else / properties / refresh_meta / properties / created_at
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedOutput schema / else / properties / refresh_meta / properties / finished_at
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedOutput schema / else / properties / refresh_meta / properties / launch_readiness
      Added value: +{
+  "$ref": "#/$defs/s3"
+}
    • addedOutput schema / else / properties / refresh_meta / properties / refresh_summary
      Added value: +{
+  "properties": {
+    "failed_connections": {
+      "items": {
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "reason": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "failed_connections_count": {
+      "type": "integer"
+    },
+    "failed_connections_has_more": {
+      "type": "boolean"
+    },
+    "launch_readiness": {
+      "$ref": "#/$defs/s3"
+    },
+    "observed_at": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "routing_errors": {
+      "type": "integer"
+    },
+    "scope": {
+      "enum": [
+        "tenant",
+        "fb_user"
+      ],
+      "type": "string"
+    },
+    "updated_assets": {
+      "properties": {
+        "ad_accounts": {
+          "$ref": "#/$defs/s0"
+        },
+        "businesses": {
+          "$ref": "#/$defs/s0"
+        },
+        "pages": {
+          "$ref": "#/$defs/s0"
+        }
+      },
+      "required": [
+        "ad_accounts",
+        "pages",
+        "businesses"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "observed_at",
+    "scope",
+    "updated_assets",
+    "failed_connections",
+    "launch_readiness"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}
    • addedOutput schema / else / properties / refresh_meta / properties / requested_scope
      Added value: +{
+  "enum": [
+    "tenant",
+    "fb_user"
+  ],
+  "type": "string"
+}
    • addedOutput schema / else / properties / refresh_meta / properties / started_at
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
  5. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false for a list operation, and the description supplies the missing rationale: 'Cache miss/authorized refresh may queue private work.' This is genuine behavioral disclosure beyond the structured fields and explains why a 'list' tool is not marked read-only. It does not, however, characterize latency or the queued work's lifecycle.

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

Conciseness3/5

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

The purpose is front-loaded and the text is compact, but the telegraphic semicolon chain and the orphan token 'assets_lookup_business_links' with no verb or connector make the routing hint hard to parse.

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 values need not be explained, and the readOnlyHint=false behavior is covered. But for a 6-parameter tool with zero schema coverage, the description omits enough parameter meaning that an agent cannot reliably construct a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, so the description must carry the load, yet it only vaguely gestures at filtering and pagination (search/cursor) and says nothing about limit, refresh, fb_user_label, or the connection_context pattern. Most parameters remain undocumented in both places.

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 with scope: 'List Facebook Pages this workspace can advertise with, with health.' Clear what it returns, but it does not distinguish itself from close siblings such as assets_list_ad_accounts, assets_list_businesses, and assets_list_instagram_accounts, so an agent must still infer which list to call.

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?

'filter then paginate' implies a workflow, and the trailing 'assets_lookup_business_links' hints at a related tool, but neither is expressed as an explicit when-to-use or when-not-to-use rule. Usage is implied rather than stated.

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