Skip to main content
Glama
Sign In
Missive MCP

Missive MCP

by kanjidoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

missive_list_conversation_drafts

Read-only

Fetch draft messages in a conversation, ordered newest first. Use pagination with the until parameter to get older drafts.

Instructions

Lists draft messages in a conversation (GET /conversations/:id/drafts), newest first. Paginate with until = delivered_at of the oldest draft 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_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of drafts to return. Default 10, max 10.
untilNoUnix timestamp: the `delivered_at` of the oldest draft from the previous page.
conversation_idYesThe conversation UUID to list drafts 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?

Description adds pagination and ordering details beyond the readOnlyHint annotation. Discloses that operation is read-only, consistent with annotation.

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 with no wasted words. Critical information (endpoint, ordering, pagination, read-only) is front-loaded and succinct.

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?

Adequate for a simple list tool with no output schema. Explains how to paginate and what parameters do. Slightly lacking in describing return format, but acceptable.

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 already describes all parameters (100% coverage). Description adds value by explaining the pagination pattern with `until` as a cursor, which is not fully clear from schema alone.

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?

Clearly states it lists draft messages in a conversation, specifies REST endpoint, ordering (newest first), and pagination. Distinguishes from sibling tools like missive_list_conversation_messages by focusing on drafts.

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 and notes read-only nature, which helps in proper invocation. However, does not explicitly guide when to use this vs other list-conversation tools.

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