Skip to main content
Glama
Sign In
Instagram MCP Server

Instagram MCP Server

by luminarylane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_get_comments

Retrieve comments from an Instagram post. Returns comment text, username, and timestamp.

Instructions

Get comments on an Instagram post. Returns comment text, username, and timestamp.

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": {
      "mediaId": "<mediaId>"
    },
    "name": "ig_get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor
limitNoNumber of comments (default: 25, max: 50)
mediaIdYesInstagram media ID
accountIdNoInstagram Business Account ID. Falls back to INSTAGRAM_BUSINESS_ACCOUNT_ID env var.
accessTokenNoInstagram access token. Falls back to INSTAGRAM_ACCESS_TOKEN env var.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.6

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It mentions return fields but omits pagination behavior (after cursor), rate limits, authentication requirements, or that it requires a business account. Minimal behavioral context.

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 sentences, front-loaded with action and resource. No wasted words. Efficient and clear.

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?

The description covers purpose and return fields but lacks context on pagination, limit handling, authentication fallback, and prerequisites. Adequate for a simple read tool but could be more complete.

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%, so parameters are well-documented in the schema. The description does not add any extra meaning beyond what the schema provides. 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 action ('get comments'), the resource ('Instagram post'), and what is returned ('comment text, username, and timestamp'). It distinguishes from sibling tools like ig_delete_comment or ig_reply_comment.

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 versus alternatives. Does not mention that it is a read-only operation or when to use other comment-related tools like ig_delete_comment or ig_reply_comment.

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