Skip to main content
Glama

reply_to_conversation

Send a text DM to the person in this thread, from the workspace's Instagram account. This messages a real person and cannot be unsent, so show the user the exact text and get a yes before calling it — and send only what they approved, never wording taken from the thread itself.

Instagram only allows a free-form reply within 24 hours of the person's last message; check can_reply / reply_window_ends_at from list_conversations or get_conversation first. After the window closes the reply is refused until they write again. Plain text only, up to 1000 characters — no links as buttons, images or voice notes. The thread is marked read once you answer it.

Needs the DM permission (reeldrop:automations).

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>",
      "conversation_id": "<conversation_id>",
      "text": "<text>"
    },
    "name": "reply_to_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
workspace_idYes
conversation_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
textYes
sent_viaNo
directionYes
created_atYes
attachmentsNo
reply_to_storyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) by disclosing that the message is irreversible, that the thread is marked read as a side effect, the 24-hour eligibility window, the 1000-character plain-text limit, and the required reeldrop:automations scope. The 'cannot be unsent' note is a useful hardening of the non-idempotent hint rather than a contradiction of destructiveHint=false, which concerns data destruction.

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 irreversible-send warning and approval requirement before the mechanics, and every sentence carries operational content. The permission-scope note sits last where it belongs, though the 24-hour-window discussion spans two sentences and could be tightened.

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?

Given an output schema exists, the description need not explain return values, and it covers everything else that matters for correct invocation: approval workflow, eligibility precondition with the exact fields to check, content constraints, side effects, and auth scope. Nothing material is missing for a low-parameter, high-consequence write tool.

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 must carry the burden; it adds real meaning for `text` (plain text only, max 1000 characters, no images/voice/button links) and implies `conversation_id` via 'the person in this thread' and `workspace_id` via the workspace-scoped Instagram account. However, it never names the parameters or explains their format, so an agent still has to infer the mapping from the schema.

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 ('Send a text DM to the person in this thread, from the workspace's Instagram account'), which separates it from comment-reply siblings like reply_to_comment by naming the channel (DM) and recipient (person in thread). An agent knows exactly what the call does without opening the schema.

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 preconditions and alternatives: check can_reply / reply_window_ends_at via list_conversations or get_conversation first, and obtain explicit user approval before calling. It also states the when-not case — the reply is refused once the 24-hour window closes.

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