Skip to main content
Glama

Find conversations

search_conversations
Read-only

Find the user's conversations by name and return summaries — id, name, message count, participants and date range. Omit query (or pass it empty) to list the most recent conversations. Pass an id from the results to get_conversation to read the transcript, or to search_messages to search the message text inside it. This matches conversation names only, not message content: to find which conversation mentions something, call search_messages without a conversation_id. Only conversations the user owns or has been shared are accessible.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional text to match against conversation names.

Output Schema

NameRequiredDescriptionDefault
next_stepNoPresent only when something stands between the user and more conversations: an empty archive (nothing to read yet) or a capture paused for billing. Relay it to the user instead of reporting that they have no conversations, or that nothing arrived.
conversationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds real value with the access-scope rule (only owned or shared conversations are visible) and the empty-query listing fallback. It omits pagination or result-size limits, which is the main remaining gap.

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?

Front-loaded with the verb, resource and return shape, and every sentence contributes distinct routing or scoping information. The routing sentences are dense but not redundant, though the paragraph could be broken up for faster scanning.

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 purpose, scope, access constraints and next-step routing, and an output schema exists so return values need no prose explanation. Pagination behavior and the cap on listing recent conversations are the only notable omissions.

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 coverage is 100% and the single parameter is documented as matching conversation names, so the schema carries most of the burden. The description adds the genuinely new behavior that query can be omitted or passed empty to list recent conversations, which is not expressed 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?

States a specific verb and resource (find conversations by name), what is returned (id, name, message count, participants, date range), and explicitly bounds the scope to names, not message content. That boundary alone separates it cleanly from search_messages without opening either schema.

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 (omit or empty query to list recent conversations), explicit when-not-to-use (name matching only, not message content), and names the alternative plus the exact condition that selects it (search_messages without a conversation_id). It also routes onward with an id to get_conversation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources