Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get comment

instagram_get_comment
Read-onlyIdempotent

Retrieve a specific Instagram comment by comment ID, including its parent ID, media ID, and replies for comment triage or reply context.

Instructions

One comment with its parent id, media id and replies.

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>"
    },
    "name": "instagram_get_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
comment_idYescomment_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description does add one piece of behavioral value beyond annotations — that replies are included in the response — but says nothing about depth/pagination of those replies or how the open-world lookup behaves when the comment is missing.

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 short clause with zero filler, and the returned payload is front-loaded. It is efficient but sits at the edge of under-specification rather than being genuinely well-structured prose.

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?

There is no output schema, so the description carries the return-value burden and does so by naming the three things the caller gets back: parent id, media id and replies. Combined with annotations that fully cover safety and idempotency and a schema that fully documents both parameters, nothing essential for a correct call is missing.

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 description coverage is 100%, with the account parameter documented (alias defaults to the configured default account) and comment_id constrained by a pattern, so the baseline of 3 applies. The description adds no meaning beyond the schema — it does not mention the account parameter, the id format, or what happens with an invalid or deleted comment_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a single-resource retrieval and names the returned fields (parent id, media id, replies), so the resource is clear. However, it is a verbless fragment that never states the operation explicitly ("retrieve"/"fetch"), and it does not name instagram_list_comments as the alternative, so differentiation from that sibling rests entirely on the name.

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?

There is no when-to-use guidance at all: nothing says this is the follow-up to instagram_list_comments when you already hold a comment_id, and nothing states prerequisites or when to prefer the list tool. The only usage signal is the implicit get-vs-list naming convention.

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