Skip to main content
Glama

ai_conversation_list

Read-onlyIdempotent

List the saved AI conversations for one subject, or fetch one with its messages. subject_type and subject_id are required so conversation history never falls back to a project-wide view. Without conversation_id it lists (most-recently-updated first; each row includes id, created_at, updated_at, message_count, summarized_message_count, and summary_updated_at). With conversation_id it fetches that single conversation — returns its summary (rolling text from compaction:"summarize", null otherwise), summary_updated_at, and the message log in chronological order. By default a fetch returns only live (non-summarized) messages, matching what the model sees on the next call; include_summarized:true also returns rows folded into the summary.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "subject_type": "<subject_type>",
      "subject_id": "<subject_id>"
    },
    "name": "ai_conversation_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Only applies when listing. Max conversations to return. Default 50, max 200.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).
subject_idYesConversation owner id. The server applies this scope to both list and single-conversation reads.
subject_typeYesConversation owner type. 'app_user' is for signed-in app users.
conversation_idNoOptional. A saved record id returned by ai_conversation_list fetches that conversation with its messages. Omitted: all conversations are listed.
include_summarizedNoOptional. Only applies when fetching one conversation: when true, also returns messages folded into the summary (the full transcript). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint; the description adds substantial behavior on top: list rows are ordered most-recently-updated first, a fetch returns the rolling summary text (null when no compaction:"summarize") plus a chronological message log, and fetches default to live-only messages with include_summarized exposing folded rows. The rationale ('matching what the model sees on the next call') clarifies why the default filters.

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 two-mode structure is front-loaded and the parallel 'Without conversation_id... With conversation_id...' construction is easy to scan. It is a dense single paragraph with several parenthetical asides; slightly tighter phrasing would improve it, but every sentence carries 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?

With no output schema, the description enumerates the returned fields for both modes (id, created_at, updated_at, message_count, summarized_message_count, summary_updated_at, summary text, chronological messages), which is exactly the detail an agent needs to interpret results. All six parameters and the required-scope constraint are covered.

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 baseline is 3; the description still adds meaning by tying conversation_id to the mode switch, explaining that subject_type/subject_id prevent a project-wide fallback, and clarifying that limit applies only when listing and include_summarized only when fetching. These cross-parameter conditions go beyond the per-field schema text.

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 first sentence states a specific verb and resource (list saved AI conversations) and immediately declares the dual-mode behavior (list vs. fetch one with messages). The subject scoping requirement is stated up front, so an agent knows exactly what this tool does without opening the schema.

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

Usage Guidelines4/5

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

The description explicitly routes between the two modes: omitting conversation_id lists, providing it fetches a single conversation. It also states the required subject scoping so history never falls back to a project-wide view. It does not name alternative tools or say when not to use this one, which keeps it short of a 5.

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