Skip to main content
Glama
Sign In
Missive MCP

Missive MCP

by kanjidoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

missive_list_conversation_comments

Read-only

Retrieve comments from a Missive conversation, ordered newest first. Use pagination with the oldest comment's creation date to fetch more results.

Instructions

Lists comments in a conversation (GET /conversations/:id/comments), newest first. Paginate with until = created_at of the oldest comment from the previous page. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of comments to return. Default 10, max 10.
untilNoUnix timestamp: the `created_at` of the oldest comment from the previous page.
conversation_idYesThe conversation UUID to list comments from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds ordering ('newest first') and pagination behavior beyond the readOnlyHint annotation. No contradictions; reinforces safety.

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 sentences, no redundant words. Each piece of information is purposeful and front-loaded.

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?

Covers core action, pagination, and idempotency. A bit more detail on return format would be helpful but is not critical given the tool's simplicity.

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 covers all parameters; description adds practical pagination guidance for 'until' and 'limit' max 10, enhancing usability beyond raw schema.

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 clearly states it lists comments in a conversation, specifying the exact HTTP endpoint. It distinguishes itself from sibling tools by focusing on comments, a distinct sub-resource.

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?

Provides pagination instructions using the 'until' parameter and notes the tool is read-only. Does not explicitly compare to alternatives, but the purpose is unambiguous.

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