Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

get_conversation_messages

Read-only

Retrieve messages from a single Instagram DM conversation by conversation ID, with optional limit and page ID, to review or analyze direct message threads.

Instructions

Messages in one DM conversation.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
page_idNo
conversation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds nothing: no ordering of messages, no pagination behavior despite a page_id parameter, and no statement about what happens for an invalid or empty conversation. With the annotation bar lower, this still leaves a substantial gap for a list tool.

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

Conciseness2/5

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

The sentence is short but that is under-specification rather than conciseness; there is no wasted wording yet no useful content either. Nothing is front-loaded because there is effectively nothing to front-load.

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?

An output schema exists, so return-value detail is not required. But for a paginated, filtered retrieval tool with three undocumented parameters and no annotation coverage of pagination, the description is too thin to let an agent call it correctly, especially around paging and conversation_id provenance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/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 compensate and it does not. It never explains conversation_id (format, where to obtain it), limit (default 25, max?), or page_id (cursor semantics). All three parameters are documented only by their bare names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment "Messages in one DM conversation" identifies the resource (messages) and narrows scope to a single DM thread, which does distinguish it from the sibling get_conversations. However, there is no verb (list/retrieve) and no statement of what is actually done with those messages, so purpose is only inferable.

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?

No when-to-use guidance is given. The description does not state that conversation_id must first come from get_conversations, nor does it mention any alternative for broader message retrieval. The agent must guess the calling context entirely.

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