AdsAgent — Meta Ads MCP

fb_users_list

Read-only

List FB users by owner_ref and label; filter then paginate. BM links: assets_lookup_business_links; accounts_find_owner is operator-only. For website settings, give Assets and connections. Ordinary users have Creatives and Assets, not full Settings. Do not send them to internal/admin pages. 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

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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.1/5.0

Behavior3/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false, lowering the transparency burden. The description confirms the read-only list operation by repeating 'List' and adding account-account usage expectations. It adds useful context about account identity and page routing, but it does not disclose behavior beyond what the annotations can convey, such as pagination mechanics, cache/refresh mechanics, or access restrictions.

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 first sentence is front-loaded and gives the core semantics, but the remaining sentences mix tool suggestions, permission notes, and an external support link. These are operationally relevant yet not all necessary for invoking fb_users_list correctly, and the description overall is noticeably longer than the primary purpose requires.

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?

With an output schema, annotations, and no required parameters, the tool is callable with only basic guidance, and the description supplies pagination intent and access rules. However, five parameters are entirely undocumented at the schema level and largely unexplained in the description, particularly refresh and search, which leaves part of the tool's behavior opaque.

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%, so the description must compensate for unannotated parameters. The phrase 'by owner_ref and label; filter then paginate' loosely maps to fb_user_label and cursor/limit concepts, but the schema has five parameters and the description never mentions search, refresh, limit, or cursor, and owner_ref is not even a schema property. This leaves the agent without meaningful semantic guidance for most parameters.

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?

The description states a specific verb and resource ('List FB users by owner_ref and label; filter then paginate', and it clearly frames the operation as a read operation. However, it references 'owner_ref as if it were a parameter when the schema only exposes fields like fb_user_label and search, which creates slight ambiguity against sibling tools. Still, it is distinct from sibling update/mutation tools.

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?

The description gives contextual guidance about which tools to use for business-manager links and when accounts_find_owner applies, and it adds access-safety instructions about ordinary users and internal/admin pages. However, it does not explicitly state when to prefer fb_users_list over alternatives or provide a clean 'use when vs. use instead' rule. Usage guidance is implied rather than formally 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 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?