Twist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

search-content

Read-onlyIdempotent

Find threads, comments, and messages across a Twist workspace. Filter results by channel, author, date, or mentions to locate specific discussions.

Instructions

Search across a workspace for threads, comments, and messages. Supports filtering by channels, authors, dates, and mentions.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return.
`query`	Yes	The search query string.
`cursor`	No	Cursor for pagination.
`dateTo`	No	End date for filtering (YYYY-MM-DD).
`dateFrom`	No	Start date for filtering (YYYY-MM-DD).
`authorIds`	No	Filter by author user IDs.
`channelIds`	No	Filter by channel IDs.
`mentionSelf`	No	Filter by mentions of current user.
`workspaceId`	Yes	The workspace ID to search in.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes
`query`	Yes
`cursor`	No
`hasMore`	Yes
`results`	Yes
`workspaceId`	Yes
`totalResults`	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

A3.6/5.0

Behavior3/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive, covering the main safety profile. The description adds useful scope about the content types searched (threads, comments, messages) and available filters, but it does not describe return format, pagination behavior, or other operational details.

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?

The description is two concise sentences with no filler. The main purpose is front-loaded, and the filter capability is summarized efficiently, making it easy for an agent to parse quickly.

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?

For a read-only search tool with complete parameter descriptions and an output schema, the description is largely sufficient. It covers what is searched and the key filtering dimensions. The only notable gap is lack of explicit guidance on how this tool relates to overlapping sibling tools, but that is more of a usage-guidance concern.

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 parameters are already well documented. The description's mention of filtering by channels, authors, dates, and mentions adds a helpful summary but does not provide semantic detail beyond what the schema already supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action and resource: searching across a workspace for threads, comments, and messages. It communicates the tool's scope without being a mere restatement of the name, though it does not explicitly differentiate itself from sibling tools like get-mentions or load-thread.

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 usage through 'Search across a workspace' and mentions supported filters, which gives agents a reasonable sense of when to invoke it. However, it does not explicitly state when not to use it or name alternatives, especially since get-mentions overlaps with the mention filter.

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