AdsAgent — Meta Ads MCP

products_get_funnel_values

Read-only

Read per-ad funnel values

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "products_get_funnel_values"
  }
}

Input Schema

Name	Required	Default
`date_to`	No
`date_from`	No
`attribution`	No	value
`product_ref`	No
`product_name`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- removedInput schema / properties / connection_context
```
Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}
```
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"
+}
```

Changed3 schema fields changedSep 11, 2026

addedOutput schema / else / properties / funnel_semantics / properties / empty_funnel_interpretation
```
Added value: +{
+  "const": "no_selected_events_returned_not_zero_proof"
+}
```
addedOutput schema / else / properties / funnel_semantics / properties / read_coverage_scope
```
Added value: +{
+  "const": "query_result_not_upstream_ingestion"
+}
```

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 / funnel_semantics

Added value: +{
+  "properties": {
+    "coverage_requirement": {
+      "const": "verify_insights_and_source_coverage"
+    },
+    "missing_event_implies_missing_insights": {
+      "const": false
+    },
+    "missing_event_is_zero": {
+      "const": false
+    },
+    "representation": {
+      "const": "sparse"
+    }
+  },
+  "type": "object"
+}

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 already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds no behavioral context at all — no scoping, no required identifiers, no empty-result behavior. It essentially restates the read-only nature already in the annotations without contributing anything new.

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 four-word phrase is maximally concise and front-loaded, but here brevity is under-specification rather than efficiency. No sentence is wasted, but too few are present to do the job.

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 needn't be described, but for a five-parameter tool with zero schema coverage and a crowded product/funnel sibling group, the description leaves too much unresolved. The agent cannot confidently select or parameterize this tool from the definition alone.

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 five parameters (date_from, date_to, attribution with default "value", product_ref, product_name), so the description carries the full burden and delivers almost nothing. "Per-ad" hints at aggregation scope but doesn't explain attribution's meaning, the date format, or whether product_ref/product_name identify the target product.

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?

It has a verb ("Read") and a resource ("per-ad funnel values"), but "funnel values" is jargon that isn't defined, and nothing distinguishes it from siblings like products_get_funnel_candidates, products_funnel_prepare, or products_get_actions. An agent can guess it retrieves funnel data but not what a "funnel value" actually is.

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 when-to-use guidance, no mention of the prepare/confirm funnel workflow (products_funnel_prepare / products_funnel_confirm) that surrounds it, and no exclusion criteria. The agent must infer placement in the workflow entirely from the name.

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?