Skip to main content
Glama
exileum

meta-mcp

ig_get_media_insights

Retrieve analytics for a specific Instagram media post, using current metrics like views, reach, saved, shares, likes, comments, reposts, and reels_skip_rate.

Instructions

Get insights/analytics for a specific media post. Note: 'impressions' and 'video_views' were deprecated in v22.0 — use 'views' instead. Available metrics: views, reach, saved, shares, likes, comments, reposts, reels_skip_rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
media_idYesMedia ID
metricNoComma-separated metrics (default: views,reach,saved,shares). For REEL add: likes,comments,reposts,reels_skip_rate
Behavior3/5

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

Discloses deprecated metrics from v22.0 but does not discuss authentication, rate limits, or behavior on invalid media_id. With no annotations, more behavioral context would be beneficial.

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 concise sentences, front-loaded with purpose, then includes critical metric details. No wasted words.

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?

Covers purpose, metrics, and deprecations, but lacks description of return format or other behavioral aspects. With no output schema, a bit more detail would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds value beyond schema by explaining deprecated metrics, default metric values, and additional metrics for reels. Schema coverage is 100%, so baseline is 3, but this extra context lifts to 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it gets insights/analytics for a specific media post, distinguishing it from sibling tools like ig_get_account_insights or ig_get_media_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides notes on deprecated metrics, default metric, and reel-specific metrics, but does not explicitly state when to use vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/exileum/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server