AdsAgent — Meta Ads MCP

mmp_insights_get_product_today

Read-only

Read today's D0 cohort; channel_pid required

Input Schema

TableJSON Schema

Name	Required	Description	Default
`today`	No
`event_keys`	No
`channel_pid`	Yes
`product_ref`	No
`product_name`	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"
+}
```

Changed2 schema fields changedSep 11, 2026

addedOutput schema / $defs / sa

Added value: +{
+  "properties": {
+    "can_report_stored_total": {
+      "type": "boolean"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "zero_proven": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "can_report_stored_total",
+    "zero_proven",
+    "reason"
+  ],
+  "type": "object"
+}

addedOutput schema / else / properties / read_evidence

Added value: +{
+  "description": "Proofs apply independently to returned metrics and scope as stored/observed. A new read_ref is a call identifier, never a source watermark. False or missing proof means unknown, not zero. Fingerprints correlate requests/results in audits; they are not authorization or pagination tokens.",
+  "properties": {
+    "artifact_returned": {
+      "type": "boolean"
+    },
+    "configuration": {
+      "properties": {
+        "account_inventory_enumerated": {
+          "const": false
+        },
+        "all_campaigns_paused_proven": {
+          "const": false
+        },
+        "requested_ids_complete": {
+          "type": "boolean"
+        },
+        "scope": {
+          "const": "requested_entity_ids_only"
+        }
+      },
+      "type": "object"
+    },
+    "mmp": {
+      "properties": {
+        "can_report_scoped_totals": {
+          "type": "boolean"
+        },
+        "provider_cache_max_age_seconds": {
+          "const": 90
+        },
+        "reason": {
+          "type": "string"
+        },
+        "scope": {
+          "const": "linked_apps_queried_channels_and_windows"
+        },
+        "source_observed_at": {
+          "type": "null"
+        }
+      },
+      "type": "object"
+    },
+    "read_ref": {
+      "pattern": "^read_[0-9a-f]{32}$",
+      "type": "string"
+    },
+    "request_fingerprint": {
+      "type": "string"
+    },
+    "result_fingerprint": {
+      "type": "string"
+    },
+    "scopes": {
+      "items": {
+        "properties": {
+          "all_campaigns_paused_proven": {
+            "const": false
+          },
+          "funnel": {
+            "additionalProperties": {
+              "$ref": "#/$defs/sa"
+            },
+            "maxProperties": 32,
+            "type": "object"
+          },
+          "index": {
+            "type": "integer"
+          },
+          "inventory_anchor": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "inventory_coverage": {
+            "type": "string"
+          },
+          "inventory_source_observed_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "metrics": {
+            "additionalProperties": {
+              "$ref": "#/$defs/sa"
+            },
+            "type": "object"
+          },
+          "metrics_source_observed_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "range_complete": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "scope": {
+            "const": "stored_query"
+          }
+        },
+        "type": "object"
+      },
+      "maxItems": 10,
+      "type": "array"
+    }
+  },
+  "required": [
+    "read_ref",
+    "request_fingerprint",
+    "result_fingerprint"
+  ],
+  "type": "object"
+}

First observedSep 9, 2026

TDQS

C2.9/5.0

Behavior3/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 safety profile is covered. The description adds the data-scope framing ('today's D0 cohort'), which is meaningful context, but says nothing about auth requirements, rate limits, or what 'D0' entails. With annotations carrying safety, a 3 is appropriate.

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 compact statement with the required-parameter note front-loaded and no filler. It is well-sized and easy to scan, though its brevity shades into under-specification rather than pure efficiency.

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 6-parameter analytics tool with 0% schema coverage, the description is far too thin: it never defines 'D0' or explains the roles of event_keys, product_ref, product_name, or connection_context. The output schema covers return values, but the input contract and the tool's relationship to its cohort/event siblings remain unaddressed.

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 6 parameters, so the description carries the full burden. It only flags channel_pid as required and leaves today, event_keys, product_ref, product_name, and connection_context completely unexplained, including the ambiguous product_ref vs product_name distinction. It does not compensate for the coverage gap.

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?

States a specific verb and resource: 'Read today's D0 cohort.' The scope is concrete enough that an agent knows it returns today's cohort data. It doesn't explicitly distinguish itself from close siblings like mmp_insights_query_product_cohort or mmp_insights_get_product_event_today, but the 'today/D0' framing is reasonably specific.

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?

The only guidance is 'channel_pid required,' which is a parameter constraint, not usage direction. There is no statement of when to use this versus mmp_insights_query_product_cohort or mmp_insights_get_product_event_today, nor any prerequisites or exclusions. The agent is left to infer selection entirely.

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?