Skip to main content
Glama
inbox-recall

inbox-recall

by joey12725

List conversations

list_conversations
Read-only

Lists chats by recent activity with message counts, date spans, and participants, so you can filter conversations by title, network, person, or time range.

Instructions

List chats, most recently active first, with message counts, date span and the people in them. Filter by title, network, a person in the chat, or activity in a time range.

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": "list_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenNoOnly chats with messages in this time range.
limitNo
queryNoChat title fragment.
cursorNo
formatNotext: compact, citation-tagged transcript (default). json: the full structured result.text
personNo
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the result ordering, the fact that each row includes message counts, date span and participants, and the implicit pagination surface. It does not explain cursor semantics, but that is a modest gap.

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?

Two tight sentences with zero filler, and the shape of the result is front-loaded before the filtering options. Nothing needs trimming.

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?

With no output schema, the description carries the burden of describing return values, and it does so compactly (counts, date span, participants). The main omission is how cursor-based paging behaves, which matters for a 7-parameter list tool.

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 only 43%, so the description must carry more weight. It does map roughly onto query, person, network and when, but leaves cursor and the array semantics of person/network undocumented in both places. Partial compensation for the coverage gap warrants a 3.

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 gives a specific verb and resource ("List chats") plus ordering ("most recently active first") and the summary fields returned (message counts, date span, people). It does not explicitly contrast itself with siblings such as get_conversation or search_messages, so it stops short of a 5.

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 filter clause ("Filter by title, network, a person in the chat, or activity in a time range") implies when the tool is appropriate, but there is no statement of when not to use it or which sibling handles message-level search or single-chat retrieval. Usage is inferable rather than explicit.

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