Twist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

fetch-inbox

Read-onlyIdempotent

Fetch a complete inbox view for a workspace, including threads, conversations, unread counts, and unread IDs. Filter by date, unread status, or archive state.

Instructions

Fetch inbox view with threads, conversations, unread counts, and unread IDs. Provides a complete picture of the inbox state. Use archiveFilter "all" to include threads marked as done alongside active threads.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of items to return.
`sinceDate`	No	Optional date to get items since (YYYY-MM-DD format).
`untilDate`	No	Optional date to get items until (YYYY-MM-DD format).
`onlyUnread`	No	Only return unread items.
`workspaceId`	Yes	The workspace ID to fetch inbox for.
`archiveFilter`	No	Filter inbox threads by archive status. "active" (default) shows only current threads, "archived" shows only done/archived threads, "all" shows both active and done threads.	active

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes
`threads`	Yes
`unreadCount`	Yes
`workspaceId`	Yes
`totalThreads`	Yes
`conversations`	Yes
`unreadThreads`	Yes
`totalConversations`	Yes
`unreadConversations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv7.0.0Aug 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv5.5.1Jul 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds behavioral detail beyond annotations by specifying that the response includes unread counts and IDs and clarifying how archiveFilter affects which threads are included.

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?

The first sentence is front-loaded and informative, and the final sentence provides a concrete parameter usage tip. The middle sentence, 'Provides a complete picture of the inbox state,' is somewhat redundant with the first sentence and could be removed without losing information.

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

Completeness5/5

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

The combination of a fully described schema, rich annotations, and an output schema means the description does not need to explain parameters or return structure in depth. The description adds the key behavioral nuance about archiveFilter, and there are no obvious gaps that would prevent an agent from calling the tool correctly.

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?

Schema description coverage is 100%, so the schema already documents all six parameters, including defaults and enum meanings. The description's mention of archiveFilter 'all' adds little beyond the schema's existing enum description, so it earns the baseline score rather than extra credit.

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 a specific verb and resource: 'Fetch inbox view' and enumerates the contents (threads, conversations, unread counts, unread IDs). This distinguishes it from sibling tools like load-thread or load-conversation, which target individual items rather than the aggregate inbox state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for getting a complete picture of the inbox, and it gives specific guidance about using archiveFilter 'all' to include done threads. However, it does not explicitly contrast this tool with siblings such as get-mentions, search-content, or load-conversation, or state when one would be preferred over another.

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