instagram-mcp

Overview Schema Source Related Servers Discussions Admin

Get Instagram comment

instagram_get_comment

Read-only

Fetch a specific Instagram comment by ID to view its moderation status, parent context, and replies. Returns text as untrusted and omits undisclosed fields.

Instructions

Fetch a single comment by id, including its moderation state (hidden), parent/media context, and inline replies (repliesTruncated=true when Instagram returned only the first page of them). Comment text and usernames are returned as fenced, untrusted text. Fields Instagram does not disclose are omitted rather than nulled; a deleted comment returns an error. A reply Instagram returns without an id is left out, and omittedWithoutId plus note say how many were.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account`	No	Name of the configured account profile to operate as (multi-account). Omit to use the default profile (IG_ACTIVE_PROFILE).
`commentId`	Yes	The Instagram comment id to fetch (e.g. an id from instagram_list_comments).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`note`	No
`text`	No
`media`	No
`hidden`	No
`replies`	No
`username`	No
`parent_id`	No
`timestamp`	No
`like_count`	No
`omittedWithoutId`	No
`repliesTruncated`	No	True when Instagram has more replies than it returned inline; replies then lists only the first page and no tool here reads the rest.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.8.0Oct 16, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / commentId / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```

addedOutput schema / $defs

Added value: +{
+  "__schema0": {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "like_count": {
+        "type": "number"
+      },
+      "replies": {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      "repliesTruncated": {
+        "description": "True when Instagram has more replies than it returned inline; replies then lists only the first page and no tool here reads the rest.",
+        "type": "boolean"
+      },
+      "text": {
+        "type": "string"
+      },
+      "timestamp": {
+        "type": "string"
+      },
+      "username": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  }
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / properties / media / additionalProperties
```
Previous value: -trueNew value: +{}
```
addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / omittedWithoutId

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / replies / items / $ref
```
Added value: +"#/$defs/__schema0"
```
removedOutput schema / properties / replies / items / additionalProperties
```
Removed value: -true
```

removedOutput schema / properties / replies / items / properties

Removed value: -{
-  "id": {
-    "type": "string"
-  },
-  "like_count": {
-    "type": "number"
-  },
-  "replies": {
-    "items": {
-      "$ref": "#/properties/replies/items"
-    },
-    "type": "array"
-  },
-  "text": {
-    "type": "string"
-  },
-  "timestamp": {
-    "type": "string"
-  },
-  "username": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / replies / items / required
```
Removed value: -[
-  "id"
-]
```
removedOutput schema / properties / replies / items / type
```
Removed value: -"object"
```

addedOutput schema / properties / repliesTruncated

Added value: +{
+  "description": "True when Instagram has more replies than it returned inline; replies then lists only the first page and no tool here reads the rest.",
+  "type": "boolean"
+}

First observedv0.7.0Aug 30, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that text and usernames are fenced untrusted data, that undisclosed fields are omitted rather than nulled, that a deleted comment errors, and that replies are truncated (repliesTruncated) or dropped without an id (omittedWithoutId plus note). That is exactly the kind of edge-case behavior an agent needs.

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?

Front-loads purpose in the first clause, then layers edge cases efficiently; every sentence carries information. It is dense and reads as a single long paragraph rather than being broken up, which slightly hurts scannability.

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?

With an output schema present, the description needn't restate field shapes, yet it covers the return semantics that matter (truncation, omission, untrusted text, error on deleted comment) and the account-selection model is handled by the schema. Nothing needed to call it correctly 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%, so both parameters (commentId, account) are already documented in the schema and the baseline is 3. The description adds no additional meaning about the parameters themselves.

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 ('Fetch a single comment by id') plus the scope of what comes back (moderation state, parent/media context, inline replies). It is clearly distinguishable from siblings like instagram_list_comments or instagram_get_media.

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

Usage Guidelines3/5

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

The 'by id' framing and the schema's hint that the id comes from instagram_list_comments imply the use case, but the description never explicitly says when to prefer this over listing comments or how it relates to instagram_reply_to_comment / instagram_hide_comment. Usage is inferable rather than stated.

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