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

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

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, and the word "Read" is consistent with them (no contradiction). However, the description adds nothing beyond that safety profile – no mention of pagination, caching, auth/connection requirements, or what "actions" actually contain.

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?

A single short sentence that is front-loaded and free of filler, but it is under-specified rather than genuinely concise – the brevity comes at the cost of nearly all useful 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?

An output schema exists so return values need not be described, but with three undocumented parameters, no usage guidance, and an ambiguous purpose, the definition leaves an agent unable to confidently call this tool in the funnel-setup workflow it references.

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% across three parameters (limit, cursor, connection_context), so the description carries the full burden and provides no parameter meaning at all. limit/cursor imply a paginated list, but the description never confirms pagination semantics or explains the connection_context token pattern.

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?

"Read Meta actions for funnel setup" essentially restates the tool name (get_actions) with a vague scope qualifier. "Meta actions" is ambiguous – it could mean Facebook/Meta platform objects or generic action records – and it does not distinguish this tool from the many sibling products_* tools like products_get_funnel_values or products_get_top_campaigns.

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 statement of when to use this tool, what triggers it in a workflow, or which alternative to prefer. The phrase "for funnel setup" hints at a context but gives no condition for selection against the other products_* or insights_* tools.

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?