Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

reply_to_comment

Replies publicly to a top-level Instagram comment using a comment ID and message, helping campaigns engage audiences and manage conversations through the official Graph API.

Instructions

Reply publicly to a top-level comment.

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

Input Schema

NameRequiredDescriptionDefault
messageYes
comment_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.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 this is a non-read-only, non-destructive, non-idempotent, open-world write. The description adds real value by noting the reply is public, which matters for a mutation tool. It says nothing about rate limits, permission requirements, or that repeating the call creates duplicate public replies.

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 eight-word sentence with the key constraint front-loaded and no filler. It is efficient, though the extreme brevity is what leaves the other dimensions thin.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 not be explained, but for a public write tool with zero schema description coverage the definition is under-specified: the meaning of comment_id and message remain undocumented, and there is no mention of failure modes such as replying to a non-top-level comment.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters, so the description carries the burden. It only hints that comment_id must identify a top-level comment; it says nothing about message formatting, length limits, or what a valid comment_id looks like.

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?

States a specific verb and resource ('reply publicly to a comment') and adds the constraint that only top-level comments are valid targets, which distinguishes it from generic commenting siblings like comment_on_media. It is clear but does not explicitly name an alternative tool.

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 phrase 'top-level comment' implicitly tells the agent this tool is for top-level threads only, which is useful scoping. However, there is no explicit when-to-use versus get_comments/comment_on_media guidance, and no prerequisites such as needing an existing comment or account permissions.

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