Skip to main content
Glama
subzeroid

HikerAPI — Instagram MCP

by subzeroid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v2_media_comments_replies

Read-only

Fetch replies under an Instagram comment to read the full thread. Pass media_id and comment_id, then paginate with min_id to load more responses.

Instructions

Get replies under one comment of an Instagram post. Use it to read a thread; use get_v2_media_comments for the top-level comments. Pass media_id and comment_id (both from the comments tool); paginate with min_id from the previous response. Live request to Instagram, billed per call. (GET /v2/media/comments/replies)

Input Schema

NameRequiredDescriptionDefault
min_idNo
media_idYes
safe_intNoConvert all big integers to strings
comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / safe_int
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Convert all big integers to strings",
+  "title": "Safe Int"
+}
  2. First observedv1.0.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only/open-world/non-destructive, but the description adds cost and latency context that annotations cannot: 'Live request to Instagram, billed per call', plus the underlying endpoint. It doesn't mention rate limits or response shape, but for a read tool the added cost disclosure is genuinely useful.

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?

Three tight sentences plus an endpoint tag; purpose, routing, parameter provenance, and cost are all front-loaded with no filler.

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?

For a paginated read endpoint with no output schema, the description supplies everything needed to call it correctly: required inputs and their source, the pagination mechanism, and the cost model.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate, and it does: it explains that media_id and comment_id both come from the comments tool and that min_id is the pagination cursor from the previous response. Only safe_int is left to its schema description.

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?

States a specific verb and resource ('Get replies under one comment of an Instagram post') and explicitly contrasts with the sibling top-level comments tool. An agent can distinguish it from get_v2_media_comments without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('read a thread') and names the alternative tool for the other case ('use get_v2_media_comments for the top-level comments'). It also states where the required IDs come from, removing inference.

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