Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

get_account_insights

Read-only

Retrieve Instagram account-level insights for up to 30 days, including reach, views, engagement, interactions, likes, comments, saves, shares, replies, follows, and profile link taps.

Instructions

Account-level insights. Default metrics: reach, views, accounts_engaged, total_interactions. Others: likes, comments, saves, shares, replies, follows_and_unfollows, profile_links_taps. since/until: ISO dates (max 30 days).

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

Input Schema

NameRequiredDescriptionDefault
sinceNo
untilNo
periodNoday
metricsNo
breakdownNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond that by disclosing the default metric set and the maximum 30-day window, which strongly shapes how an agent should call it. It says nothing about rate limits, pagination, or empty-result behavior, so it stops short of rich behavioral context.

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?

Front-loaded with the resource, then defaults, then alternatives, then the date constraint — a sensible order with no filler sentences. The long metric enumeration is functional but consumes most of the text.

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

Completeness5/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 not be described, and the annotations cover the read-only/open-world profile. Given that, the description supplies what an agent actually needs to invoke correctly — metric vocabulary, defaults, and the date-range cap — with only the 'period' and 'breakdown' parameters left unaddressed.

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 0%, so the description must carry the parameter burden, and it partially does: it enumerates valid metric values, identifies the defaults, and constrains since/until to ISO dates within 30 days. However, it never explains 'period' (day/week/days_28) or 'breakdown', leaving two of five parameters with no semantic guidance anywhere.

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 phrase 'Account-level insights' names the resource and implicitly scopes it against the sibling get_media_insights, and the metric list makes clear what is retrieved. It lacks an explicit verb ('retrieve'/'get') and never states the resource is Instagram/account analytics, but the intent is unambiguous.

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 statement of when to call this versus get_media_insights, get_account_pages, or collect_insights, and no prerequisites or exclusion cases. The only guidance is which metrics exist and the 30-day date limit, which is parameter information rather than usage routing.

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