Skip to main content
Glama
exileum

meta-mcp

ig_get_media_insights

Read-only

Retrieve analytics for an Instagram media post, with metrics like views, reach, and interactions tailored to media type.

Instructions

Get insights/analytics for a specific media post. Default metrics 'views,reach' are safe for every media type. Metric availability differs by media type — request more selectively to avoid (#100) errors:

  • IMAGE / VIDEO / CAROUSEL: views, reach, saved, total_interactions, likes, comments (note: 'shares' may return (#100) on IMAGE — test before relying on it)

  • REEL: views, reach, saved, total_interactions, likes, comments, shares, reposts, reels_skip_rate

  • STORY: views, reach, total_interactions, navigation, replies, profile_activity, profile_visits, follows Note: 'impressions' and 'video_views' were deprecated in v22.0 — use 'views' instead. See https://developers.facebook.com/docs/instagram-platform/reference/instagram-media/insights/ for the authoritative per-type matrix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricNoComma-separated metrics. Default 'views,reach' is universally supported; override per media type per the tool description.views,reach
media_idYesMedia ID
Behavior5/5

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

The description discloses metric availability differences, potential (#100) errors, and deprecation of 'impressions' and 'video_views'. Annotations already indicate readOnlyHint=true and openWorldHint=true, which are consistent. No contradictions.

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?

Description is front-loaded with purpose, then organized with bullet points for metric availability by media type. Every sentence adds value, including the deprecation note and link to authoritative docs. No fluff.

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?

Although no output schema, the description explains exactly what metrics can be retrieved per media type. Provides a link for authoritative matrix. For a read-only analytics tool with clear metric lists, it is complete.

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

Parameters5/5

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

Input schema coverage is 100% with descriptions for both parameters. The description adds significant meaning beyond schema by detailing metric options per media type, which is not in the schema. Default metrics 'views,reach' are explained as universally safe.

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?

The description clearly states it gets insights/analytics for a specific media post, distinguishing from siblings like ig_get_account_insights (account-level) and ig_get_media (basic info). The verb 'Get' and specific resource 'insights for a specific media post' provide clear purpose.

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

Usage Guidelines5/5

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

Provides explicit guidance on default metrics vs selective metrics per media type to avoid (#100) errors. Lists metric availability for IMAGE, VIDEO, CAROUSEL, REEL, and STORY, with notes on deprecations. This helps the agent choose the correct metrics.

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