Instagram MCP Server

get_comments

Get all comments on an Instagram post, including text, author, timestamp, like count, and replies. Provides comment IDs for replying, hiding, or deleting comments.

Instructions

List comments on a post.

Returns id, text, username, timestamp, like_count, and replies (if any). Use the comment IDs with reply_to_comment, hide_comment, or delete_comment.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max comments to return
`media_id`	Yes	Media ID from list_recent_media

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Describes what the tool does (list comments) and what fields are returned. No annotations exist, but the description adequately covers the read-only behavior without contradictions.

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 sentences, no waste. First sentence states purpose, second adds key details and links to other tools. Concise and well-structured.

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

Completeness5/5

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

Description mentions all relevant return fields and next-step tools. Output schema exists, so return format clarity is sufficient. No gaps.

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 covers both parameters fully (100%). Description adds minimal extra meaning beyond restating the resource. Baseline 3 is appropriate.

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?

Description clearly states 'List comments on a post' with a specific verb and resource. Differentiates from sibling tools like reply_to_comment, hide_comment, and delete_comment.

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

Usage Guidelines4/5

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

Tells user what fields are returned and how to use the output (with other tools). Does not explicitly compare to alternative listing tools but provides actionable next-step guidance.

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