Skip to main content
Glama
kanjidoc
by kanjidoc

missive_list_conversations

Read-only

Retrieve conversations from your Missive team inbox filtered by mailbox, label, team, or contact. Results sorted by newest activity, with pagination support.

Instructions

Lists conversations visible to the API-token user (GET /conversations), newest activity first. REQUIRES at least one mailbox filter: a boolean (inbox, all, assigned, closed, snoozed, flagged, trashed, junked, drafts) or an ID filter (shared_label, team_inbox, team_closed, team_all). organization is an optional filter (falls back to MISSIVE_DEFAULT_ORGANIZATION, omitted otherwise). email/domain/contact_organization are mutually exclusive. Paginate with until = last_activity_at of the oldest conversation from the previous page. Read-only. Conversations where you are only a guest return just id and last_activity_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoPass true to list conversations in the All mailbox.
emailNoFilter by a specific contact email address (e.g. user@example.com). Mutually exclusive with `domain` and `contact_organization` — pass at most one of the three.
inboxNoPass true to list conversations in the Inbox.
limitNoNumber of conversations to return. Default 25, max 50.
untilNoUnix timestamp used to paginate: the `last_activity_at` of the oldest conversation from the previous page.
closedNoPass true to list conversations in Closed.
domainNoFilter by contacts from an email domain (e.g. example.com, no leading @). Mutually exclusive with `domain` and `contact_organization` — pass at most one of the three.
draftsNoPass true to list conversations in Drafts.
junkedNoPass true to list conversations in Spam (a.k.a. Junk).
flaggedNoPass true to list conversations in Starred (flagged).
snoozedNoPass true to list conversations in Snoozed.
trashedNoPass true to list conversations in Trash.
assignedNoPass true to list conversations assigned to the user.
team_allNoTeam ID. List conversations in the team's All mailbox.
team_inboxNoTeam ID. List conversations in the team's Inbox.
team_closedNoTeam ID. List conversations in the team's Closed mailbox.
organizationNoOptional organization ID filter. Falls back to MISSIVE_DEFAULT_ORGANIZATION; omitted entirely when neither is set. No effect when a shared_label or team_ filter is used.
shared_labelNoShared label ID. List conversations carrying this shared label.
contact_organizationNoContact organization/group UUID to filter by. Mutually exclusive with `domain` and `contact_organization` — pass at most one of the three.
Behavior4/5

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

Annotations declare readOnlyHint=true, and description adds that guest users only get id and last_activity_at. Also states 'Read-only', reinforcing the annotation. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph but efficient, front-loading the main action and then detailing constraints. Every sentence adds value, though could be slightly more structured with bullet points.

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 filtering requirements, pagination, guest behavior, and fallbacks. No output schema exists, but the description adequately addresses what the agent needs to use the tool correctly.

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 good descriptions. The tool description adds extra context: requirement for at least one filter, mutual exclusivity, and pagination technique using 'until'.

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 conversations visible to the API-token user, newest activity first. Distinguishes from sibling list tools by specifying the resource (conversations) and the filter requirements.

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 at least one mailbox filter, lists all filter options, and notes mutual exclusivity among email/domain/contact_organization. Also explains pagination. Does not explicitly exclude scenarios but provides clear context for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kanjidoc/missive-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server