AdsAgent — Meta Ads MCP

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "assets_list_pages"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`search`	No
`refresh`	No
`fb_user_label`	No

Output Schema

Name	Required	Description	Default
`message`	No
`retryable`	No
`support_ref`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- removedInput schema / properties / connection_context
```
Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}
```
Changed6 schema fields changedOct 15, 2026
- 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"
+}
```
Changed1 schema field changedOct 13, 2026
- addedOutput schema / else / properties / items / items / properties / whatsapp_connected
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```

Changed7 schema fields changedSep 10, 2026

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"
+  ]
+}
```

First observedSep 9, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Adds real context beyond annotations: 'Cache miss/authorized refresh may queue private work' explains why readOnlyHint is false on a list operation and warns about asynchronous side effects. It stops short of saying what 'private work' produces or how long it takes.

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?

Very compact and front-loaded: purpose first, then side-effect caveat, then workflow hint. The final bare tool name without a connecting phrase costs a bit of readability but no sentence is wasted.

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 no explanation, and the side-effect caveat covers the main behavioral risk. However, with five undocumented parameters and an unexplained 'authorized refresh' concept, an agent still lacks enough to call it confidently in non-default cases.

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 coverage is 0%, so the description must compensate, but it only gestures at 'filter' (search) and 'paginate' (limit/cursor) without naming or explaining them. The refresh flag and fb_user_label are left entirely unexplained, as are the limit bounds.

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: 'List Facebook Pages this workspace can advertise with, with health.' The scope ('this workspace', 'can advertise with') distinguishes it from generic page listings like fb_users_list, though the sibling differentiation is implicit rather than spelled out.

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 call pattern, but the trailing 'assets_lookup_business_links' is a dangling reference with no verb or condition explaining when to prefer it. No explicit when-not or prerequisites are given.

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 tools Inspect

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

Need Help?