Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

post_comments

Read-only

Reads comments on an Instagram post so you can review them and decide which ones to reply to before using the reply tool.

Instructions

Baca komentar-komentar sebuah post. Pasangan baca dari post_reply_to_comment: baca dulu, putuskan, baru balas.

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": {
      "url": "<url>"
    },
    "name": "post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and side-effect profile are covered. The description adds only the read-before-reply workflow and says nothing about pagination, ordering, or how many comments come back by default despite the openWorld hint. That is a modest value-add over the structured fields.

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 short sentences, no waste, with the core purpose front-loaded ahead of the workflow pointer. Nothing could be removed without losing information.

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

Completeness3/5

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

For a simple read-only list tool with no output schema the description is adequate, but with zero schema coverage it should at least explain what 'limit' does and roughly what a call returns. The openWorld hint suggests unpredictable result volume that is never addressed.

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?

Schema description coverage is 0% for both parameters, so the description must carry the burden and does not. It implies 'url' identifies the post but never explains the format, and the 'limit' parameter is not mentioned at all, leaving half the inputs undocumented.

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?

Names a specific verb+resource ('Read the comments of a post') and explicitly positions itself as the read-side counterpart of post_reply_to_comment. It does not distinguish itself from post_comment (which presumably creates one), so it is clear but not fully differentiated from all siblings.

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?

Gives an explicit workflow: read first, decide, then reply, and names the alternative tool post_reply_to_comment for the reply step. It stops short of stating when NOT to use it (e.g., when you only want a single comment via post_get), but the sequencing guidance is concrete.

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