Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

get_media_insights

Read-only

Retrieve performance insights for a single Instagram post, with metrics automatically selected for feed posts, Reels, or Stories unless you specify them.

Instructions

Insights for one post. Metrics are picked automatically for feed posts, Reels or Stories unless given.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_id": "<media_id>"
    },
    "name": "get_media_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricsNo
media_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/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 the non-obvious default behavior that metrics are auto-selected based on post type (feed, Reels, Stories), which is real value beyond the annotations, but says nothing about limits or partial-data behavior.

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 short sentences, front-loaded with what the tool returns, then the one behavioral fact an agent cannot infer. Nothing is redundant or padded.

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

Completeness4/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. For a two-parameter read tool this is nearly complete; the only remaining gap is the lack of guidance on valid metric identifiers and when to override the automatic selection.

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 schema alone leaves both parameters opaque. The description rescues the 'metrics' parameter by explaining that it is optional and defaults to type-based auto-selection, but leaves media_id and the accepted metric names/format unexplained.

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 first sentence names a specific verb-resource pair ('Insights for one post'), and the scoping to a single post implicitly separates it from account-level siblings like get_account_insights. It stops short of naming the sibling it should not be used for, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The definition tells the agent how metric selection works ('picked automatically ... unless given') but never states when to prefer this over get_account_insights or collect_insights. Usage is only implied by the phrase 'for one post'.

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