Skip to main content
Glama
exileum

meta-mcp

ig_get_replies

Read-only

Retrieve replies to a specific Instagram comment using its comment ID. Supports pagination and field selection.

Instructions

Get replies to a specific comment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor for next page
limitNoNumber of replies to return
beforeNoPagination cursor for previous page
fieldsNoComma-separated fields (default: id,text,username,timestamp,like_count,hidden,from)id,text,username,timestamp,like_count,hidden,from
comment_idYesComment ID to get replies for
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description's 'Get replies' adds no additional behavioral context. The description does not mention pagination, rate limits, or that the tool returns a list of replies, beyond what is implied by the schema.

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?

The description is a single concise sentence with no superfluous information. It is front-loaded with the core action and resource.

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 5 parameters, no output schema, and openWorldHint, the description is too minimal. It does not specify that the tool returns a list of replies, nor does it explain the pagination behavior or any additional context needed for proper invocation.

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 detailed descriptions for each parameter (e.g., 'after: Pagination cursor for next page'). The description adds no extra meaning beyond what the schema provides, meeting the baseline.

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 'Get replies to a specific comment,' specifying the verb ('Get') and resource ('replies'). The tool name 'ig_get_replies' and description distinguish it from siblings like 'ig_get_comments' (top-level comments) and 'ig_reply_to_comment' (posting replies).

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 provides no guidance on when to use this tool versus alternatives such as 'ig_get_comments' or 'ig_get_comment'. There is no mention of context, prerequisites, or situational appropriateness.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/exileum/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server