Skip to main content
Glama

reply_to_comment

Post a PUBLIC reply under a comment on the account's post. Everyone who can see the post sees it, and it cannot be edited — only deleted from the Instagram app. Show the user the exact text and get a yes before calling it, and send only what they approved, never wording taken from a comment.

This is a public reply, not a DM: to send the commenter a private message use a comment-to-DM automation (create_automation). Up to 2200 characters.

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": {
      "workspace_id": "<workspace_id>",
      "ig_account_id": "<ig_account_id>",
      "comment_id": "<comment_id>",
      "text": "<text>"
    },
    "name": "reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
comment_idYes
workspace_idYes
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
statusYes
reply_idNo
comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing public visibility, that the reply cannot be edited and is only removable from the Instagram app, and a 2200-character cap. The annotations cover mutation/idempotency hints, and the description adds the irreversibility and audience consequences the hints cannot express; only the return behavior is left to the output schema.

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 the most consequential fact (PUBLIC, uneditable) before the approval workflow, and the second paragraph cleanly separates the DM alternative. Slightly over-punctuated with dashes and an em-dash aside, but no sentence is filler.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a public mutation with an output schema, the description covers visibility, reversibility, limits, and the approval gate — everything an agent needs to avoid a harmful call. The one real gap is identifier-level parameter guidance, which the 0%-coverage schema leaves entirely unaddressed.

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% and all four identifiers are required, yet the description only adds a length constraint for 'text'. It never explains what workspace_id, ig_account_id, or comment_id refer to or where to obtain them, so an agent still has to guess at identifier sourcing.

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 (post), resource (reply), and placement (under a comment on the account's post), with PUBLIC emphasized as the defining scope. It immediately distinguishes itself from a private-message path by naming create_automation as the DM route.

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 pre-call protocol (show the user the exact text, get a yes, send only what they approved, never wording taken from a comment) and names the alternative tool for the private-message case. Both when-to-use and when-not-to-use are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources