Skip to main content
Glama

ig_media_insights

Read-only

Retrieve Instagram post metrics by media ID, including views, reach, shares, saves, and reel average watch time, to measure content performance.

Instructions

Métricas de una publicación: views, reach, shares, saves, tiempo medio de visionado (reels)…

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoUsuario de Instagram configurado (por defecto la cuenta activa)
media_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is already covered. The description adds useful context by naming the metric set returned, but says nothing about availability limits (e.g. reels-only fields), pagination, or permission requirements on the account.

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?

A single compact sentence that front-loads the purpose and lists the metrics. The trailing ellipsis signals incompleteness of the metric list rather than consuming space wastefully.

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 read-only insight tool with no output schema, the description partially compensates by enumerating returned metrics, but it omits required identifier semantics, account scoping behavior, and any note on missing metrics for non-reel media.

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

Parameters2/5

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

Two parameters with only 50% schema description coverage: media_id has no description in the schema and none in the tool description, so the agent gets no format guidance (numeric ID vs shortcode). The description adds zero parameter meaning beyond the schema.

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?

States a specific verb+resource: returns metrics for a published media item, and enumerates representative metrics (views, reach, shares, saves, average view time for reels). It is distinguishable from ig_account_insights (account-level) and ig_media_get (media data fetch), though it never names those siblings explicitly.

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 guidance. The description does not say when to use this instead of ig_account_insights, ig_media_get, or ig_analytics, nor does it note that a valid media_id from ig_media_list is required.

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