AdsAgent — Meta Ads MCP

fb_users_list

Read-only

Read stored FB labels/status/expiry/routing, never credentials; filter then paginate. refresh rereads rows; no Meta sync, token refresh, queued work or snapshot writes. BM: assets_lookup_business_links. Access is not full Settings. Use the same AdsAgent account

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedOutput schema / else / properties / items / items / properties / connection_state

Added value: +{
+  "description": "Optional. user_disconnected = the user withdrew AdsAgent's access (data is kept, reconnect any time); needs_reauthorization = the credential expired or was invalidated.",
+  "enum": [
+    "connected",
+    "user_disconnected",
+    "needs_reauthorization",
+    "removed"
+  ],
+  "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
- 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

A3.5/5.0

Behavior4/5

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

Annotations already establish readOnly/destructive=false, so the safety bar is met; on top of that the description discloses that credentials are never returned, that refresh only re-reads existing rows, and that no Meta sync/token refresh/queueing/snapshot writes occur. 'Access is not full Settings' is useful scope context.

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?

Front-loads the core read semantics and contains no filler, but it is a run-on of semicolon-joined fragments with unexplained jargon ('BM:', 'AdsAgent account') that costs more parsing effort than the length suggests.

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 need not be described, and the negative-space disclosures are helpful. Still, for a 6-parameter tool with zero schema descriptions, key inputs like connection_context (which has a strict pattern) and cursor are left entirely unexplained.

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 coverage is 0% across 6 parameters, so the description must compensate. It partially does: 'refresh rereads rows' maps to refresh, 'filter then paginate' gestures at search/limit/cursor, and the field list hints at fb_user_label. But cursor, search, and connection_context receive no explanation at all.

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 read on stored FB users and enumerates the fields returned (labels/status/expiry/routing), explicitly excluding credentials, which is a meaningful distinction from the update/refresh siblings. The telegraphic style and cryptic 'BM: assets_lookup_business_links' shorthand muddy it slightly, but the verb+resource is identifiable.

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?

Gives a filtering-then-paginating workflow and states several things this is NOT (no Meta sync, token refresh, queued work, snapshot writes), which is genuine negative guidance. However it never says when to prefer this over fb_users_refresh_routing or fb_users_update_label, and 'Use the same AdsAgent account' is an assumption, not a routing rule.

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?