Skip to main content
Call insights_capabilities before querying. Choose the reporting period, entity level, metrics, conversion event, and attribution window. Follow query cursors before reporting complete results. The tables list arguments and common nested fields. Expand Full input schema for all fields and allowed values. Workspace and account permissions apply to every tool.

insights_capabilities

List supported metrics, reporting levels, breakdowns, and pagination settings. Access: mcp:read. Arguments: none.

insights_query

Read one page of reporting data. Call insights_capabilities to check supported combinations. Pages default to 25 rows, with a maximum of 100. Follow next_cursor with the same filters to read more. Use sorting and min_spend to narrow results, or entity_ids to inspect specific objects. For structured metrics such as actions and action_values, supply both action_types and attribution_windows. For example, use action_types: ["omni_purchase"] and attribution_windows: ["7d_click"] for purchases attributed within seven days of a click. Choose these values to match the report you need. Daily account, campaign, and ad-set totals can aggregate compatible metrics from ad rows. Reach and frequency use the requested reporting level. Access: mcp:read.

insights_rank

Rank performance over a date range. Choose one reporting level, then use global for a combined ranking across accounts or per_account for separate rankings. Conversion metrics require an explicit event and attribution window. Set minimum spend or conversion filters to exclude low-data results. highest and lowest refer to numeric values; lower CPA can be better. This tool returns compact rankings without pagination. Access: mcp:read.