AdsAgent — Meta Ads MCP

accounts_list_linked_accounts

Read-only

List account routing; filter then paginate. BM links: assets_lookup_business_links; accounts_find_owner is operator-only

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.

Changed13 schema fields changedSep 10, 2026

addedOutput schema / $defs

Added value: +{
+  "s0": {
+    "items": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": [
+            "null",
+            "string"
+          ]
+        }
+      },
+      "required": [
+        "id"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "s2": {
+    "properties": {
+      "count": {
+        "type": "integer"
+      },
+      "has_more": {
+        "type": "boolean"
+      },
+      "items": {
+        "$ref": "#/$defs/s0"
+      }
+    },
+    "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 / items / items / properties / pages / $ref
```
Added value: +"#/$defs/s0"
```

removedOutput schema / else / properties / items / items / properties / pages / items

Removed value: -{
-  "properties": {
-    "id": {
-      "type": "string"
-    },
-    "name": {
-      "type": [
-        "null",
-        "string"
-      ]
-    }
-  },
-  "required": [
-    "id"
-  ],
-  "type": "object"
-}

removedOutput schema / else / properties / items / items / properties / pages / type
```
Removed value: -"array"
```
addedOutput schema / else / properties / items / items / properties / pixels / $ref
```
Added value: +"#/$defs/s0"
```

removedOutput schema / else / properties / items / items / properties / pixels / items

Removed value: -{
-  "properties": {
-    "id": {
-      "type": "string"
-    },
-    "name": {
-      "type": [
-        "null",
-        "string"
-      ]
-    }
-  },
-  "required": [
-    "id"
-  ],
-  "type": "object"
-}

removedOutput schema / else / properties / items / items / properties / pixels / type
```
Removed value: -"array"
```
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/s2"
+        },
+        "businesses": {
+          "$ref": "#/$defs/s2"
+        },
+        "pages": {
+          "$ref": "#/$defs/s2"
+        }
+      },
+      "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

C2.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a hint about pagination ('then paginate') and a routing/BM-links context, but it is too fragmented to provide meaningful behavioral detail beyond the annotations.

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

Conciseness2/5

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

The description is short but not concise in a useful way; it is a fragmented, ungrammatical string that reads like notes rather than a structured definition. It is not front-loaded with the core purpose and contains cryptic references that waste the agent's attention.

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

Completeness2/5

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

For a list tool with 5 optional parameters, no schema descriptions, and an output schema, the description should clarify what is being listed, how pagination works, and what the search/refresh/label parameters do. It does none of this. The output schema exists but the description still fails to provide the minimal context needed to call the tool correctly.

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 carries the full burden for explaining the 5 parameters. It fails to explain limit, cursor, search, refresh, or fb_user_label. The only hint is 'then paginate', which vaguely relates to cursor/limit but adds no concrete semantics.

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

Purpose2/5

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

The description is a garbled fragment: 'List account routing; then paginate. BM links: assets_lookup_business_links; accounts_find_owner is operator-only'. It does not state a clear verb+resource. The title 'Accounts List Linked Accounts' suggests listing linked accounts, but the description text is incoherent and fails to distinguish this tool from siblings like assets_lookup_business_links or accounts_get_account_detail.

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

Usage Guidelines2/5

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

The description mentions 'BM links: assets_lookup_business_links' and 'accounts_find_owner is operator-only', which hints at alternatives, but the guidance is cryptic and lacks a clear when-to-use statement. It does not explain when to choose this tool over accounts_list_eligible_pages or assets_lookup_business_links.

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?