AdsAgent — Meta Ads MCP

products_get_actions

Read-only

Read Meta actions for funnel setup

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 10, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / cursor
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / limit

Added value: +{
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / else / properties / has_more
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / else / properties / meta

Added value: +{
+  "properties": {
+    "continuation_source": {
+      "type": "string"
+    },
+    "cursor_expires_at": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "metrics_authoritative": {
+      "type": "boolean"
+    },
+    "snapshot_complete": {
+      "type": "boolean"
+    },
+    "source": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / else / properties / next_cursor

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / else / properties / returned_count
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / else / properties / total_count
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / else / properties / usage

Added value: +{
+  "const": "funnel_configuration_only"
+}

addedOutput schema / else / properties / usage_note
```
Added value: +{
+  "type": "string"
+}
```

First observedSep 9, 2026

TDQS

C2.7/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 minimal behavioral context ('for funnel setup') but does not disclose pagination behavior, response shape, or any side effects. This is acceptable for a read-only tool but not especially rich.

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?

The description is a single short sentence with no wasted words. It is front-loaded and easy to parse, though it is arguably too terse to fully carry its meaning.

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?

With no parameter descriptions, no usage guidance, and only a vague resource phrase, the description leaves the agent to infer how to call the tool correctly. The output schema and annotations help, but the description itself is not complete enough for a tool with two undocumented parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain 'limit' or 'cursor' at all. The schema provides only names, types, and a min/max range; the description adds no meaning about how pagination works or what values are appropriate.

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 uses a clear verb ('Read') and names the resource ('Meta actions for funnel setup'). It is specific enough to distinguish this from sibling tools like products_get_health or products_get_top_campaigns, though it does not explicitly contrast itself with any sibling.

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?

There is no guidance on when to use this tool versus alternatives such as products_get_funnel_values or products_save_funnel_events. The description only states what the tool reads, not when it should be chosen or what conditions favor it.

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?