Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by lupikovoleg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_comment_replies

Retrieve nested replies for a comment on an Instagram reel or post by providing the comment ID and media URL.

Instructions

Get nested replies for a specific comment on a reel or post.

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": {
      "comment_id": "<comment_id>",
      "media_url": "<media_url>"
    },
    "name": "get_comment_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYes
media_urlYes
page_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

No annotations provided, so the description bears full burden. It does not disclose behaviors like pagination, handling of empty replies, or rate limits. Minimal beyond the core action.

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 sentence is efficient, but lacks structure. No paragraphs or bullet points, but gets the point across without waste.

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

Completeness2/5

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

With 3 parameters, no annotations, and an output schema, the description is too minimal. It doesn't explain pagination, output format, or how to handle optional parameters.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no explanation for parameters (comment_id, media_url, page_id). It does not clarify that page_id is for pagination.

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?

The description clearly states the tool retrieves nested replies for a comment on a reel or post, distinguishing it from siblings like get_media_comments (top-level comments) and get_comment_likers (likers).

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 description implies use when nested replies are needed, but lacks explicit guidance on when not to use it or alternatives. No mention of pagination or prerequisites.

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