Meta Ads by Get MCP Ads

meta join product insights

meta_join_product_insights

Read-onlyIdempotent

Query product-breakdown Meta Ads insights and join rows with Product Catalog metadata to enrich reporting when catalog access is available.

Instructions

Query product-breakdown insights and enrich rows with Product Catalog metadata when catalog access is available.

Input Schema

Name	Required	Description	Default
`level`	No	Entity or aggregation level for the requested report.	ad
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`metrics`	No	Native or documented calculated metric names to request. Check compatibility with the selected dimensions.
`catalogId`	No	Product Catalog ID used to load product metadata for joins.
`timeRange`	No	Optional custom insights date range.
`datePreset`	No	Insights date preset. Defaults to last_30d.
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)
`productBreakdown`	No	Native product grouping used to join catalog items with reported insights.	product_id
`catalogProductLimit`	No	Maximum catalog product records read for the join.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / timeRange / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv2.0.1Sep 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral context beyond that: the catalog join is opportunistic and degrades gracefully when catalog access is unavailable, which tells the agent rows may come back unenriched. It does not mention rate limits or pagination, but those live in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the primary verb and resource, then the conditional enrichment clause. No filler, no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no explanation, and nine parameters are fully documented in the schema. The description covers the one thing the schema cannot convey — that catalog enrichment is conditional — leaving only minor gaps such as default date-preset behavior and metric/dimension compatibility.

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

Parameters3/5

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

Schema description coverage is 100%, with enums, defaults, bounds and nested timeRange all documented inline, so the baseline is 3. The description adds no syntax or format guidance for catalogId, productBreakdown, or catalogProductLimit beyond what the schema already states.

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 states a specific verb and resource ('query product-breakdown insights') plus a secondary behavior ('enrich rows with Product Catalog metadata'), which clearly separates it from the generic meta_get_insights sibling. It stops short of naming an alternative tool, but the 'product-breakdown' scoping makes the domain unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the product-breakdown framing and the conditional 'when catalog access is available', which signals a prerequisite. However, it never explicitly says to prefer this over meta_get_insights for product-level reporting, nor does it name meta_get_catalog_products as the catalog-side alternative, so routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server