Skip to main content
Glama
exileum

meta-mcp

ig_get_comments

Read-only

Fetch comments on an Instagram media post by providing a media ID. Supports pagination and custom field selection.

Instructions

Get comments on a specific Instagram media post.

Input Schema

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

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (varying response). The description adds no behavioral details like pagination, authentication needs, or whether it returns a list or single comment.

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

Conciseness3/5

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

One concise sentence (8 words), but lacks structure. It is efficient but could include more contextual information without being verbose.

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?

Missing explanation about return format (list), pagination support, or how it relates to sibling tools like ig_get_comment. Tool has 5 parameters and no output schema, so more detail is needed.

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 descriptions for all parameters. The description adds no additional meaning beyond the schema, so 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?

The description clearly states the verb 'Get', the resource 'comments', and the scope 'on a specific Instagram media post'. It distinguishes from sibling tools like ig_get_comment (singular) and ig_get_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?

No guidance on when to use this tool vs alternatives such as ig_get_comment or ig_get_replies. No mention of prerequisites or context for usage.

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