instagram-mcp-server

Get Conversation

instagram_get_conversation

Read-onlyIdempotent

Retrieve messages from one Instagram conversation, newest first, so you can review recent replies and verify the 24-hour response window before replying.

Instructions

Read the messages in one conversation, newest first.

Note the 24-hour rule before replying: a standard reply is only allowed within 24 hours of the user's most recent message. Check the newest created_time to see whether the window is still open.

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": "instagram_get_conversation"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum messages to return
`conversation_id`	Yes	Conversation ID from instagram_list_conversations
`response_format`	No	'markdown' for readable text, 'json' for structured data	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds useful ordering semantics ("newest first") and the 24-hour messaging policy, but says nothing about pagination or whether more messages exist beyond the limit, which matters for a message-listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and the operational caveat in a clearly separated second paragraph. No filler or restatement of the tool name.

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?

For a read-only single-conversation reader with full schema coverage and no output schema, the description supplies the ordering guarantee and references the created_time field the agent must inspect. The only minor omission is pagination behavior, which is low-risk against a limit parameter capped at 100.

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 100%, so conversation_id, limit and response_format are already documented in the schema, including the enum values for response_format. The description adds no extra meaning about parameter interaction, such as what happens when limit is reached. Baseline 3 applies.

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?

The description opens with a specific verb and resource ("Read the messages in one conversation") plus a result ordering ("newest first"). That is enough to separate it from instagram_list_conversations, which enumerates conversations rather than reading one conversation's messages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete use case: check the newest created_time here to determine whether the 24-hour reply window is still open before replying. It does not state exclusions or name a sibling tool for the alternative path (e.g., listing conversations to find an ID), so it stops short of full when/when-not guidance.

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

Deploy Server