Skip to main content
Glama

Get ad insights

ads_get_insights
Read-only

Return daily performance for an ad account, or for one campaign, ad set or ad when objectId is given. For TikTok, breakdown returns an audience breakdown (age, gender, country_code or platform) instead of the daily series.

Input Schema

NameRequiredDescriptionDefault
levelNoTikTok: the level of objectId (campaign, ad_group or ad). Defaults to campaign.
sinceNoYYYY-MM-DD. Give both since and until, or neither for the default range.
untilNoYYYY-MM-DD, on or after since, at most 730 days later.
objectIdNoA campaign, ad set or ad id from ads_get_tree. Defaults to the whole ad account.
platformNometa_ads or tiktok_ads. Needed only when the profile has both ad networks and no accountId is given.
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
breakdownNoTikTok only: return an audience breakdown instead of the daily series.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.
adAccountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / adAccountId / pattern
      Previous value: -"^act_\\d+$"New value: +"^(act_)?\\d+$"
    • addedInput schema / properties / breakdown
      Added value: +{
      +  "description": "TikTok only: return an audience breakdown instead of the daily series.",
      +  "enum": [
      +    "age",
      +    "gender",
      +    "country_code",
      +    "platform"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / level
      Added value: +{
      +  "description": "TikTok: the level of objectId (campaign, ad_group or ad). Defaults to campaign.",
      +  "enum": [
      +    "campaign",
      +    "ad_group",
      +    "ad"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "meta_ads or tiktok_ads. Needed only when the profile has both ad networks and no accountId is given.",
      +  "enum": [
      +    "meta_ads",
      +    "tiktok_ads"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / accountId / description
      Previous value: -"The Facebook accountId from list_accounts. Defaults to the profile's Facebook connection."New value: +"The Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection."
    • changedInput schema / properties / profileId / description
      Previous value: -"Defaults to the profile your API key is bound to."New value: +"A profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Read-only and open-world behavior is already declared by annotations, so the bar is lower. The description still contributes real behavioral context: output shape switches between a daily time series and an audience breakdown depending on breakdown and platform, which is non-obvious and not obvious from a per-parameter schema alone.

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 sentences, no filler, and the primary behavior (daily performance plus scoping by objectId) is front-loaded before the TikTok-specific exception. Nothing redundant.

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, yet the description never says what the daily series or breakdown actually contains (metrics, granularity, pagination). For a 9-parameter analytics tool the description leaves the return shape underspecified.

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 coverage is 89%, so the schema carries parameter meaning; the description only echoes the objectId scoping and breakdown mode without adding format, defaults, or constraints beyond it.

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 names a specific verb and resource ('Return daily performance') and defines two scopes: the whole ad account by default, or a single campaign/ad set/ad when objectId is passed. It is clear enough to distinguish from CRUD siblings like ads_update_account, though it never names a competing analytics sibling such as get_facebook_page_metrics.

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?

It gives an implied when-to-use rule (pass objectId to narrow to one object; pass breakdown for TikTok audience splits), but it never says when to prefer this over ads_get_tree, ads_get_account, or get_tiktok_account_insights, which an agent choosing among analytics tools would need.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources