AdsAgent — Meta Ads MCP

products_list

Read-only

List products and funnel/MMP event sources

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`channel_pid`	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.

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

Changed1 schema field changedOct 8, 2026

addedOutput schema / else / properties / meta / properties / metric_completeness

Added value: +{
+  "additionalProperties": {
+    "properties": {
+      "complete": {
+        "type": "boolean"
+      },
+      "excluded_rows": {
+        "type": "integer"
+      },
+      "reason": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 11, 2026

addedOutput schema / else / properties / workspace_ref

Added value: +{
+  "description": "Opaque workspace comparison hint; not an authorization credential.",
+  "pattern": "^workspace_[0-9a-f]{32}$",
+  "type": "string"
+}

Changed1 schema field changedSep 10, 2026
- addedOutput schema / else / properties / meta / properties / data_freshness / properties / last_pull_scope
```
Added value: +{
+  "const": "workspace"
+}
```
First observedSep 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations cover the safety profile (readOnly, non-destructive, closed-world), but the description adds nothing beyond that—no mention of pagination behavior despite limit/cursor params, no scoping context, no relationship to funnel/MMP sources. With annotations present the bar is lower, but there's still little added value.

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?

A single short phrase with no waste. Appropriately sized, though it is so terse it omits necessary information.

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?

Four undocumented parameters at 0% coverage, pagination via cursor, a channel_pid filter, and a connection_context token all go unexplained. Funnel/MMP relationship is ambiguous. Even with an output schema, the input semantics are far under-specified.

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 carry the burden. It doesn't explain limit hard cap, cursor semantics, what channel_pid filters, or what the connection_context pattern means. The funnel/MMP mention hints at channel_pid relevance but adds no clarifying detail.

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

Purpose3/5

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

The verb 'List' and resource 'products' are clear, but the addition of 'funnel/MMP event sources' muddies whether it lists products, event sources, or both. It also doesn't differentiate from siblings like setup_analyze_products or mmp_get_state.

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?

No indication of when to use this versus alternatives such as setup_analyze_products or the mmp_* tools. The agent is left to infer usage.

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?