Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get media

instagram_get_media
Read-onlyIdempotent

Retrieve details for a single Instagram media item by media ID, including caption, type, permalink, counts, URLs, alt text, username, and carousel children; Stories are supported.

Instructions

Details of one media item: caption, type, permalink, counts, URLs, shortcode, alt text, username and carousel children. Works for Stories too (comment-related fields are null there).

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": "instagram_get_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
media_idYesInstagram media id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered. The description adds real context beyond them: the tool works for Stories and comment-related fields come back null in that case, which is exactly the kind of caveat an agent needs to interpret results.

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 with zero waste; the field inventory comes first and the Stories/null caveat second. Nothing is repeated from the title or annotations.

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?

No output schema exists, so the description carries the return-value burden and does so by listing the fields returned, including carousel children. Minor gaps: no error behavior for an unknown media_id and no note on whether insights require a separate call.

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 coverage is 100% with only two parameters, both fully documented in the schema (account alias default, media_id pattern). The description adds no meaning about media_id format or the account-alias fallback, so baseline 3 applies.

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: details of ONE media item, then enumerates the returned fields (caption, type, permalink, counts, URLs, shortcode, alt text, username, carousel children). This distinguishes it from instagram_list_media by the singular scope, though it never names the sibling it is not.

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 only implied: you call it when you already have a media id and need its full record. No explicit when/when-not guidance against instagram_list_media, instagram_get_media_insights, or instagram_download_media, and no note that a media_id (not a shortcode) is required.

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

Deploy Server

Other Tools