Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get conversation

instagram_get_conversation
Read-onlyIdempotent

Fetch up to 20 messages from one Instagram conversation, newest first, with participants and 24-hour reply-window status to review and respond to DMs.

Instructions

Messages of one conversation (newest first, max 20) with participants and the 24 h window state. senders is api, webhooks or unavailable (Meta withheld sender fields).

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

NameRequiredDescriptionDefault
limitNoDefault 20, max 20.
accountNoAccount alias; defaults to the configured default account.
conversation_idYesconversation_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its budget elsewhere: result ordering, the hard 20-message cap, the presence of participants, and the critical caveat that senders may be "unavailable" because Meta withheld sender fields. That last note is genuinely non-obvious behavior an agent would otherwise misread as an error.

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?

Two dense sentences with no filler, and the primary facts (content, ordering, cap) are front-loaded before the senders caveat. The backticked `senders` reference is slightly terse but still readable.

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?

With no output schema, the description carries the burden of describing return content, and it does name the key fields (messages, participants, 24h window state, senders). The remaining gap is pagination or how to reach messages older than the 20 newest, which matters for a capped list 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 100%, so all three parameters are already documented, including the limit maximum of 20. The description only echoes the cap rather than adding new meaning (e.g., how to retrieve older messages beyond 20), so the baseline of 3 applies.

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 names a concrete verb-and-resource pair ("Messages of one conversation") and specifies scope (max 20, newest first), which clearly separates it from instagram_list_conversations. It does not explicitly call out the sibling, but the resource granularity makes the distinction obvious.

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?

Usage is only implied: fetching per-conversation messages for follow-up action. There is no statement of when to prefer this over instagram_list_conversations or instagram_get_inbox, and no prerequisites or exclusions are given.

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

Deploy Server

Other Tools