instagram-data-mcp

Overview Schema Source Related Servers Discussions Admin

instagram_highlight

Read-only

Retrieve every photo and video from a single Instagram story highlight by ID, returning signed CDN URLs for each media item.

Instructions

Get the items in one highlight. Every photo and video inside one highlight, with signed CDN URLs.

Cost: 3 credits.

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": {
      "id": "<id>"
    },
    "name": "instagram_highlight"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new behavioral context: the response contains signed CDN URLs and the call costs 3 credits, which the agent needs for budgeting and for understanding the return payload.

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 tight sentences plus a cost line; the core purpose is front-loaded and nothing is wasted. The cost disclosure is a single line that earns its place.

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?

With no output schema, the description does well to sketch the return (photos/videos with signed CDN URLs), but it omits pagination behavior for large highlights and never clarifies where the required id comes from, which is essential for a one-required-param tool.

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?

Schema coverage is 0% and the single required 'id' parameter is never explained in prose. The description doesn't say the id must be a highlight identifier or reference instagram_highlights as its source; only the schema example hints at the 'highlight:...' format. Description fails to compensate for the coverage gap.

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?

States a specific verb ('Get') and resource ('items in one highlight'), then clarifies scope with 'Every photo and video inside one highlight'. This distinguishes it from the sibling instagram_highlights (which enumerates highlights) and from instagram_posts/media, so an agent can route correctly.

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?

Usage is implied by the singular 'one highlight' phrasing, but the description never states when to use this versus instagram_highlights or how to obtain a valid highlight identifier. No exclusions, prerequisites, or alternative routing are given.

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