Skip to main content
Glama

missive

by io.usefulapi
OverviewDiscussionsAdmin

List conversations

missive_list_conversations
Read-only

List conversations (email/chat threads). Missive requires EXACTLY ONE mailbox-type filter — one of inbox / assigned / closed / flagged / snoozed / trashed / all / shared_label / team_inbox / team_all / organization. Missive: GET /conversations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoAll conversations.
emailNoFilter to conversations involving this email address.
inboxNoConversations in your inbox.
limitNoMax conversations to return (default 25, max 50).
untilNoUnix timestamp cursor — return records older than this (offset-less pagination).
closedNoClosed conversations.
flaggedNoFlagged conversations.
snoozedNoSnoozed conversations.
trashedNoTrashed conversations.
assignedNoConversations assigned to you.
team_allNoAll of a team's conversations (team id).
team_inboxNoConversations in a team's inbox (team id).
organizationNoFilter to an organization id.
shared_labelNoConversations under a shared label id.
contact_organizationNoFilter to a contact organization id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds that it uses a GET endpoint and mentions pagination via 'until' cursor. No contradictions.

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 concise sentences, no filler. The essential constraint is 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?

Without an output schema, the description explains the required filter constraint and pagination cursor, which is adequate for this list tool. Could mention limit default but it's in 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% with individual descriptions. The description adds critical context that exactly one of the filter booleans/strings must be provided, which is not captured in the 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 'List conversations (email/chat threads)' using a specific verb and resource. The sibling tools include getters for single conversations and other entities, so this tool is well-distinguished.

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?

Explicitly requires exactly one mailbox-type filter, listing the valid options. However, it does not mention when not to use this tool or alternative tools for other filtering needs.

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

All missive toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources