Skip to main content
Glama

Adbloop Meta Ads

by com.adbloop
OverviewDiscussionsAdmin

get_insights

Read-only

Rate-limit-safe Meta performance metrics (spend, impressions, clicks, CTR, leads, purchases, ROAS, frequency). Read-only. Set time_increment=1 for a day-by-day trend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoReport granularity: 'overview' = whole-account totals; 'campaign' = per campaign; 'adset' = per ad set; 'ad' = per ad. Defaults to 'campaign'.
limitNoMax number of rows to return.
sinceNoCustom range start, YYYY-MM-DD. Use together with 'until' (both required) instead of date_preset.
untilNoCustom range end, YYYY-MM-DD. Use together with 'since'.
campaign_idNoLimit the report to a single campaign (and its ad sets/ads when level is adset or ad).
date_presetNoDate-range shorthand, e.g. today, yesterday, last_7d, last_14d, last_30d, this_month, last_month, maximum. Ignored when both since and until are supplied.
time_incrementNoDaily trend mode. Set to 1 for a day-by-day series (spend, frequency, ctr, cpm per day). Combine with level 'ad' for per-ad creative-fatigue trends.
meta_account_idNoAd account to report on (defaults to your primary).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / time_increment
      Added value: +{
+  "description": "Daily trend mode. Set to 1 for a day-by-day series (spend, frequency, ctr, cpm per day). Combine with level 'ad' for per-ad creative-fatigue trends.",
+  "type": "number"
+}
  2. Changed7 schema fields changed
    • addedInput schema / properties / campaign_id / description
      Added value: +"Limit the report to a single campaign (and its ad sets/ads when level is adset or ad)."
    • addedInput schema / properties / date_preset / description
      Added value: +"Date-range shorthand, e.g. today, yesterday, last_7d, last_14d, last_30d, this_month, last_month, maximum. Ignored when both since and until are supplied."
    • addedInput schema / properties / level / description
      Added value: +"Report granularity: 'overview' = whole-account totals; 'campaign' = per campaign; 'adset' = per ad set; 'ad' = per ad. Defaults to 'campaign'."
    • addedInput schema / properties / limit / description
      Added value: +"Max number of rows to return."
    • addedInput schema / properties / meta_account_id / description
      Added value: +"Ad account to report on (defaults to your primary)."
    • addedInput schema / properties / since / description
      Added value: +"Custom range start, YYYY-MM-DD. Use together with 'until' (both required) instead of date_preset."
    • addedInput schema / properties / until / description
      Added value: +"Custom range end, YYYY-MM-DD. Use together with 'since'."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description adds a rate-limit safety guarantee, which is a useful operational trait. It also discloses the returned metric set and the day-by-day behavior of time_increment=1. It does not describe return shape or pagination, but for a read-only insights tool this is a minor gap.

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?

Two short sentences pack the key facts—safety, read-only status, metric scope, and the trend-mode hint—without filler. The most decision-relevant information is front-loaded.

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?

For a read-only query tool with fully documented optional parameters, the description covers the metric scope and a key invocation pattern. The only notable omission is a comparison with the similarly named get_segment_insights, but the schema and metric list make correct invocation achievable.

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%, so all 8 parameters are already explained in the input schema. The description's time_increment hint duplicates what the schema already says ('Set to 1 for a day-by-day series') and adds no new parameter-level meaning.

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 clearly identifies the tool as returning Meta performance metrics and enumerates the specific metrics (spend, impressions, clicks, CTR, leads, purchases, ROAS, frequency), making the purpose concrete. It does not explicitly differentiate from the sibling get_segment_insights, but the metric list makes the general function evident.

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?

The description gives a concrete invocation hint ('Set time_increment=1 for a day-by-day trend') and signals safety ('Rate-limit-safe', 'Read-only'), but it never states when to prefer this tool over siblings like get_segment_insights or get_delivery_health. Usage context is implied rather than explicit.

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

All Adbloop Meta Ads toolsInspect
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