AdsAgent — Meta Ads MCP

assets_list_ad_accounts

Read-only

List cached accounts; filter then paginate. BM links: assets_lookup_business_links

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe read. The description adds that accounts are 'cached' (implying possible staleness) and the processing order, which are valuable beyond annotations. It does not contradict annotations.

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

Conciseness5/5

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

Two sentences with no wasted words. The primary action ('List cached accounts') is front-loaded, followed immediately by usage order and a pointer to a related sibling. Efficient and well-structured.

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 read-only list tool with five optional parameters and zero schema descriptions, the description is insufficient. It does not clarify parameter meanings, the effect of refresh, or what 'cached' implies for data freshness. While an output schema exists, the agent needs parameter semantics to invoke correctly. The reference to BM links is helpful but does not fill the gaps.

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. It hints at filtering ('filter') and pagination ('paginate'), which likely map to search, limit, and cursor, but it does not explain refresh or fb_user_label at all. The description gives only a vague operation order, leaving four of five parameters unexplained. This is inadequate given the absence of schema descriptions.

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

Purpose5/5

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

The description states a specific verb ('List'), a clear resource ('cached accounts'), and a distinguishing characteristic (filtering/pagination). It is distinct from sibling tools like assets_list_businesses and assets_list_pages, and the title reinforces 'Ad Accounts'. The 'BM links' reference further differentiates it from accounts_lookup_business_links.

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

Usage Guidelines4/5

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

It gives clear operational guidance: filter then paginate, indicating the order of operations. It also references assets_lookup_business_links for BM links, implying when that sibling should be used instead. However, it does not explicitly say when to use this tool versus other account-related tools like accounts_get_account_detail or accounts_find_owner, but the scope is obvious enough.

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?