Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

insights

Read-onlyIdempotent

Retrieve performance metrics for a Meta ad account, campaign, ad set, or ad using date ranges, fields, breakdowns, and paging.

Instructions

Get performance insights for the ad account, a campaign, an ad set, or an ad.

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": "insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPaging cursor from a previous result.
levelNo
limitNo
fieldsNoComma-separated Graph API fields.
filteringNo
object_idNoNumeric object ID. Default: the configured ad account.
breakdownsNoExample: publisher_platform,platform_position.
time_rangeNo
date_presetNoExample: last_7d, last_30d, maximum.
time_incrementNo1 for daily rows, monthly, or all_days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds nothing behavioral on top of that: no mention of pagination (despite an 'after' cursor), row-explosion from breakdowns, API rate limits, or the Graph API requirement for a date_preset or time_range. For a 10-parameter reporting call this is thin.

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 front-loaded sentence with no filler or redundancy. It is efficiently written, but the brevity is achieved by omission rather than by disciplined compression of necessary detail.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should at minimum say what kind of results come back and how rows are shaped — it does not. Combined with 10 parameters, nested objects, and moderate schema coverage, the definition is under-specified for a reporting tool, though annotations and schema carry enough that an experienced Graph API caller could still invoke it.

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 coverage is only 60% across 10 parameters, including a nested time_range object, yet the description says nothing about any parameter. The level list mirrors the existing 'level' enum rather than adding meaning, so it does not compensate for the undocumented fields such as filtering, breakdowns, time_increment, or the date_preset/time_range interaction.

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?

Uses a specific verb ('Get') plus a named resource ('performance insights') and enumerates the four levels it can operate at (account, campaign, ad set, ad). That distinguishes it reasonably well from the generic 'get' and the targeting_search siblings, though it never explicitly contrasts itself with them.

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 or when-not-to-use guidance and no named alternative. The enumeration of levels implies you must pick a scope, but nothing tells the agent when to call 'insights' versus 'get' or 'targeting_search', nor what prerequisites exist.

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