Instagram120 MCP Server

reels

Fetch Instagram reels from any user by ID or username. Paginate through reels using the maxId parameter to get the next set of 12 reels.

Instructions

Get Instagram reels by user ID or username. The maxId parameter is optional and allows you to paginate through reels. By specifying the maxId (end_cursor) from the previous response, you can retrieve the next 12 reels.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reels"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 4, 2026

TDQS

C2.2/5.0

Behavior1/5

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

The description references a 'maxId' parameter not present in the input schema, creating a contradiction. No annotations are provided, and the description fails to disclose authentication, rate limits, or response format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences but suffers from misleading information about maxId. Not concise because of inaccuracies.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations, and empty input schema. The description does not explain how to specify user ID/username, making it very incomplete.

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?

The schema has no parameters (100% coverage empty), but the description implies user ID/username and maxId. The description adds pagination semantics but contradicts 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?

The description clearly states it retrieves Instagram reels by user ID or username, which is a specific verb+resource. However, it does not differentiate from sibling tools like 'posts' or 'stories'.

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?

The description mentions pagination with maxId but does not explain when to use this tool over alternatives. The parameter guidance is inconsistent with the schema.

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

Deploy Server