Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

get_comments

Read-only

Retrieve top-level comments and their first-level replies from an Instagram post by media ID to review engagement and moderate conversations.

Instructions

Top-level comments on a post (with first-level 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": {
      "media_id": "<media_id>"
    },
    "name": "get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
media_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/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 the safety profile is covered structurally. The description does add non-obvious behavior: replies are nested inside top-level comments and only first-level replies are returned (deeper threads are excluded). It says nothing about pagination or ordering despite a limit parameter, which is the main remaining behavioral gap.

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 tight fragment with zero filler, and the scope qualifier is right next to the resource. It is arguably too terse rather than padded, so the brevity is a virtue here, though the missing verb makes it read as a caption rather than an instruction.

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?

An output schema exists, so return values need no explanation, and annotations cover the read-only profile. The gaps are the undocumented media_id format and limit semantics plus the absence of any routing guidance toward sibling comment tools. Adequate for a two-parameter read, but not more than that.

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 0%, so the description carries the burden — and it only partially does. 'on a post' implies media_id but doesn't name it or state its expected form (media ID vs. shortcode vs. URL). The limit parameter and its default of 50, including whether it caps top-level comments or total items, are entirely unaddressed.

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?

The description names the resource (comments) and, more usefully, the exact scope: top-level comments plus their first-level replies. That scope qualifier is what separates it from a generic comment or conversation reader. It lacks an explicit verb (list vs. fetch) and never names a sibling, so it stops short of a 5.

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?

Usage is only implied by the resource name — an agent can infer 'use this when you want the comments on a post.' There is no statement of when not to use it and no pointer to the adjacent comment tools (reply_to_comment, delete_comment, hide_comment) or to get_conversation_messages. Implied context only.

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