Skip to main content
Glama
mikusnuz

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_get_account_insights

Retrieve Instagram account performance insights, including views, reach, follower count, interactions, and audience breakdowns, for a chosen period to analyze engagement and growth.

Instructions

Get Instagram account insights. Note: 'impressions', 'email_contacts', 'phone_call_clicks', 'text_message_clicks', 'get_directions_clicks', 'website_clicks', 'profile_views' were deprecated in v22.0. Use 'views', 'reach', 'follower_count', 'reposts' instead.

Input Schema

NameRequiredDescriptionDefault
sinceNoStart date (Unix timestamp or ISO 8601)
untilNoEnd date (Unix timestamp or ISO 8601)
metricYesComma-separated metrics: views,reach,follower_count,reposts,accounts_engaged,total_interactions
periodYesAggregation period
breakdownNoComma-separated breakdowns supported by the metric, e.g. media_product_type, follow_type, age, country
timeframeNoRequired for demographics metrics; do not combine with since or until. Engaged/reached audience demographics only support this_week and this_month; follower demographics support all listed values.
metric_typeNoAggregation type. Defaults to total_value for metrics that require it, such as views and reposts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.2
    • addedInput schema / properties / breakdown
      Added value: +{
+  "description": "Comma-separated breakdowns supported by the metric, e.g. media_product_type, follow_type, age, country",
+  "type": "string"
+}
    • addedInput schema / properties / metric_type
      Added value: +{
+  "description": "Aggregation type. Defaults to total_value for metrics that require it, such as views and reposts.",
+  "enum": [
+    "time_series",
+    "total_value"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / timeframe
      Added value: +{
+  "description": "Required for demographics metrics; do not combine with since or until. Engaged/reached audience demographics only support this_week and this_month; follower demographics support all listed values.",
+  "enum": [
+    "last_14_days",
+    "last_30_days",
+    "last_90_days",
+    "prev_month",
+    "this_month",
+    "this_week"
+  ],
+  "type": "string"
+}
  2. First observedv2.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: metrics deprecated in v22.0 and their replacements. It says nothing about the read-only nature, required permissions, rate limits, or whether metrics can be freely combined, which are material for an insights call.

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?

Two sentences, purpose front-loaded, followed by a dense but high-value deprecation warning. The long enumeration of deprecated metric names is bulky but each item earns its place as a concrete API trap to avoid.

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?

For a 7-parameter analytics tool with no annotations and no output schema, the description is thin: it never indicates what the response contains or how metric/breakdown/period interact beyond what the schema says. The rich schema compensates substantially, but behavioral and routing context is still missing.

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 100% and the schema already documents metric lists, period enums, timeframe constraints and metric_type defaults in detail, so the baseline is 3. The description's metric list largely duplicates the schema, though the deprecation note adds information not present in the schema fields.

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 states a specific verb and resource ('Get Instagram account insights'), which is clear enough to separate it from media-level siblings by naming scope. However, it never explicitly contrasts itself with ig_get_media_insights or ig_get_profile, so the differentiation is implied by the word 'account' rather than spelled out.

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 statement and no prerequisites such as required permissions or the need for an Instagram Business account. The deprecation note guides which metric names to pass, not which tool to select, so an agent still has to infer that account-level aggregates belong here rather than in ig_get_media_insights.

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

Deploy Server

Other Tools