insta-pilot

ig_messages

Read-only

Retrieve messages from a specific Instagram conversation, newest first, to review direct messages and respond to customer inquiries.

Instructions

Mensajes de una conversación (más recientes primero).

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "ig_messages"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`account`	No	Usuario de Instagram configurado (por defecto la cuenta activa)
`conversation_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds the useful return-order fact (most recent first), but does not mention pagination behavior, limits, or account selection side effects.

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?

The description is a single, front-loaded sentence with zero waste. It is appropriately concise, though its brevity borders on under-specification rather than serving as a complete invocation guide.

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?

With no output schema and low parameter-description coverage, the description should explain return values, pagination, and parameter behavior. It only states the resource and ordering, leaving key operational details absent.

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 only 33%, and the description provides no parameter-level details beyond implying that a conversation is involved. It does not explain limit, account, or the required conversation_id, so it fails to compensate for the schema gap.

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 identifies the resource clearly: messages belonging to one conversation, with ordering (most recent first). It does not explicitly differentiate itself from siblings like ig_conversations or ig_inbox, but the scope is specific enough for an agent to understand what it does.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It does not tell the agent when to choose ig_messages over ig_conversations, ig_inbox, or other message-related siblings.

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