DialogBrain

search_threads

Read-onlyIdempotent

Find or list chat threads/conversations — by topic, participant, unread/unanswered status, or recency. Omit query to list threads by filter. For message content use search.messages; for files use search.files. since filters by recency and pairs with only_unread / only_unanswered. Each thread names the LINE it speaks from (account: id, channel, name, phone, email) and whether the owner ever really wrote there (has_real_outgoing; imported history does not count). The same person can appear once per connected number — pick the thread by account, not by title, before you messages.send.

Input Schema

Name	Required	Description
`limit`	No	Maximum threads to return.
`query`	No	Topic/keyword to search threads for. OMIT to list threads by filter.
`since`	No	ISO date (YYYY-MM-DD). Only threads with any message activity since this date (recency filter, not 'unanswered'). OMIT to skip.
`offset`	No	Number of threads to skip (for pagination, default: 0)
`channel`	No	Restrict to one channel. 'ai_panel' = the workspace's AI-panel ("My AI") chats: owner/admin see all of them, a member only their own; each has thread_id, title, owner, last_message_at (read one with messages.read_history). OMIT for the normal inbox.
`only_unread`	No	Limit to threads with unread messages. OMIT to include read threads.
`in_workspace`	No	Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
`only_unanswered`	No	Limit to threads where the last message is incoming (you haven't replied). Covers 'threads I haven't replied to'. OMIT to include answered threads too.
`participant_name`	No	Filter to threads with this participant/contact. OMIT to include everyone (do NOT pass an empty string).
`include_last_messages`	No	With only_unanswered: inline the most recent N messages (0-2) per thread so one call is enough to draft replies. Text truncated to 150 chars; full body via messages.read_history.
`only_unread_on_platform`	No	Limit to threads unread in the account's own app on the platform (the member's LinkedIn, ...), as far as the channel reports it; only_unread is unread in this inbox. OMIT to skip this filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

addedInput schema / properties / channel

Added value: +{
+  "description": "Restrict to one channel. 'ai_panel' = the workspace's AI-panel (\"My AI\") chats: owner/admin see all of them, a member only their own; each has thread_id, title, owner, last_message_at (read one with messages.read_history). OMIT for the normal inbox.",
+  "type": "string"
+}

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / only_unread_on_platform

Added value: +{
+  "description": "Limit to threads unread in the account's own app on the platform (the member's LinkedIn, ...), as far as the channel reports it; only_unread is unread in this inbox. OMIT to skip this filter.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / in_workspace

Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}

AddedSep 29, 2026
RemovedAug 1, 2026

Changed1 schema field changedJul 26, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of threads to skip (for pagination, default: 0)",
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedJul 9, 2026

addedInput schema / properties / include_last_messages

Added value: +{
+  "description": "With only_unanswered: inline the most recent N messages (0-2) per thread so one call is enough to draft replies. Text truncated to 150 chars; full body via messages.read_history.",
+  "maximum": 2,
+  "minimum": 0,
+  "type": "integer"
+}

AddedMay 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, but the description adds important nuances beyond that: each thread exposes its account line, has_real_outgoing excludes imported history, and the same person can appear once per connected number. These are meaningful behavioral caveats for interpreting and selecting results, though return/pagination behavior is not fully described.

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 dense but well front-loaded: purpose first, then alternatives, then filtering nuance, then a critical account-selection warning. Every sentence contributes routing, filtering, or interpretation guidance without filler.

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 an 11-parameter read-only search tool with rich schema descriptions and no output schema, the definition provides strong routing, filter relationships, account ambiguity warnings, and some return-field context. It is nearly complete, though it could say a bit more about result shape or pagination behavior.

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%, so the parameter descriptions already carry the baseline semantics. The tool description still adds cross-parameter meaning: query omission switches to filter listing, since pairs with only_unread/only_unanswered, and include_last_messages is specifically useful with only_unanswered. That is useful beyond the schema, but not every parameter interaction is covered.

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?

States a specific verb and resource: finding/listing chat threads/conversations, with the searchable dimensions named. It explicitly distinguishes itself from search.messages and search.files, so an agent can route correctly without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: omit query to list by filter, use search.messages for message content, use search.files for files, and pair since with unread/unanswered filters. It also warns to pick the thread by account before calling messages.send, which is a concrete usage rule.

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

All DialogBrain tools Inspect

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

Need Help?