Repovive MCP Server

Get DM messages

repovive_get_conversation_messages

Read-only

Fetch paginated messages from a direct-message conversation, newest first, to review the thread before replying.

Instructions

Read the messages in one direct-message conversation, newest page first. Use it to review a thread before replying with repovive_send_direct_message.

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

Input Schema

Name	Required	Description
`page`	No	Page number (1-based)
`page_size`	No	Messages per page
`conversation_id`	Yes	Conversation id

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the read-only and open-world behavior, and the description adds useful ordering context ('newest page first') and scopes the read to one DM thread. It does not contradict the annotations.

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, front-loaded with the core action and ordering, and the usage pointer earns its place. No filler or repetition of schema field definitions.

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 simple paginated read tool with an output schema and readOnly/openWorld annotations, the description covers the purpose, usage trigger, and behavioral nuance. Required parameters and pagination bounds are already in the schema.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value beyond the schema by clarifying that conversation is a direct-message conversation and that page delivery is newest-first, which gives meaning to page/page_size behavior.

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 names a specific verb and resource: read the messages in one direct-message conversation, and specifies the page ordering ('newest page first'). It clearly separates this from listing conversations in the sibling set by scoping to a single conversation.

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 an explicit use context: review the thread before replying with repovive_send_direct_message. It does not provide when-not-to-use guidance or directly contrast with list_conversations, but the single-conversation scope makes the intended use clear.

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

Deploy Server