time-messenger-mcp-server

get_thread_messages

Fetch the full conversation of a thread by providing its root post ID. Get all messages in chronological order to review the complete discussion.

Instructions

Get all messages in a thread

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": {
      "post_id": "<post_id>"
    },
    "name": "get_thread_messages"
  }
}

Input Schema

Name	Required	Description	Default
`post_id`	Yes	Post ID (root post of the thread)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read operation via 'Get' but does not disclose details like ordering, pagination, depth of messages (including replies), or auth requirements.

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?

The description is a single concise sentence ('Get all messages in a thread') that is front-loaded with the action and object, containing zero unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is minimally viable but leaves gaps: it does not specify the return format, message ordering, whether nested replies are included, or any pagination behavior. However, given the simplicity of the tool (one parameter), it is adequate but not rich.

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?

The input schema fully documents the single parameter post_id with the description 'Post ID (root post of the thread)', achieving 100% schema description coverage. The tool description adds no additional meaning beyond that, so the baseline score of 3 is appropriate.

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 uses a specific verb 'Get' and clearly identifies the resource as 'all messages in a thread', distinguishing it from sibling tools like get_channel_messages (channel messages) and get_thread (likely thread metadata).

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 usage guidance is provided. The description does not mention when to choose this tool over alternatives such as get_channel_messages or search_messages, nor any exclusions or prerequisites.

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