AdsAgent — Meta Ads MCP

insights_export_csv

Export or queue CSV for one bounded scope

Input Schema

TableJSON Schema

Name	Required	Default
`search`	No
`date_to`	No
`filters`	No
`group_by`	Yes
`date_from`	No
`attribution`	No
`export_mode`	No	grouped
`product_ref`	No
`product_name`	No
`ad_account_id`	No
`confirm_export`	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 / else / then / properties / category
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / expected
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / else / then / properties / failure_kind
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / responsibility_hint
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / route
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / 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

Added value: +{
+  "s0": {
+    "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 / 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/s0"
+            },
+            "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/s0"
+            },
+            "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"
+}

Changed1 schema field changedSep 11, 2026

addedOutput schema / else / else / properties

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

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=false, destructiveHint=false, and openWorldHint=false, so safety is partly covered. The description adds the 'export or queue' duality, which hints at async behavior, but never explains when it queues versus exports directly, what confirm_export (default false) gates, or what connection_context/product_ref require.

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 with the verb and avoids padding. However, its brevity comes at the cost of under-specification rather than tight communication, so it earns only a middling score.

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 12-parameter tool with 0% schema coverage and a confirmation flag, the description is far too thin; an agent cannot tell how to set scope, filters, or confirm_export from it. The presence of an output schema excuses it from describing return values, but nothing compensates for the missing parameter and usage context.

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 12 parameters, so the schema carries no meaning beyond types and enums. The description contributes only the 'one bounded scope' phrase, which loosely maps to the required group_by but explains nothing about filters, export_mode, confirm_export, or attribution.

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?

States a verb and artifact ('Export ... CSV'), which is clearer than a bare name, but 'or queue' and 'one bounded scope' are vague and never defined. It does not distinguish this from the sibling console_export_csv or insights_pull_insights, leaving the agent to guess which export path applies.

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 explicit when-to-use or when-not-to-use guidance, and no reference to the many sibling tools that also produce exports or insights. 'One bounded scope' hints at a constraint but does not say what counts as bounded or when to prefer this over console_export_csv.

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?