chat-export-server

Overview Schema Source Related Servers Discussions Admin

chats_list

Read-onlyIdempotent

Lists chat titles and IDs for a selected platform in the bound browser, with optional query filtering and pagination, so you can discover chats before retrieving full payloads.

Instructions

List chats for one platform in the bound browser (titles/ids, optional query). Prefer for discovery; use projects_chats for chats inside one project, chats_get for a full payload, chat_outline for turn indexes. Requires prior browsers_bind.

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": {
      "platform": "<platform>"
    },
    "name": "chats_list"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max chats to return (1-100)
`query`	No	Optional title/text search filter when the provider supports it
`cursor`	No	Opaque pagination cursor from a previous chats_list response; null/omit for first page
`platform`	Yes	Provider id: chatgpt \| grok \| grok-x \| claude \| copilot \| qwen \| deepseek \| perplexity
`includeProjectChats`	No	When true (default), also include chats that live inside projects/folders

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.4Nov 11, 2026

addedInput schema / properties / cursor / description

Added value: +"Opaque pagination cursor from a previous chats_list response; null/omit for first page"

changedInput schema / properties / includeProjectChats / description

Previous value: -"When true (default), also list chats inside projects via containers.*"New value: +"When true (default), also include chats that live inside projects/folders"

addedInput schema / properties / limit / description
```
Added value: +"Max chats to return (1-100)"
```

addedInput schema / properties / platform / description

Added value: +"Provider id: chatgpt | grok | grok-x | claude | copilot | qwen | deepseek | perplexity"

addedInput schema / properties / query / description

Added value: +"Optional title/text search filter when the provider supports it"

First observedv1.0.3Nov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context: the binding prerequisite and the fact that results are summary-level (titles/ids) rather than full payloads. It stops short of describing rate limits, page sizing behavior, or what an empty/unbound response looks like, which keeps it below a 5.

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?

Three short sentences, front-loaded with the core purpose, then sibling routing, then the prerequisite. No filler or restatement of the tool name; every clause carries information an agent needs before calling.

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 listing tool with full schema coverage and no output schema, the description supplies the essentials: what is returned at a summary level, how it differs from deeper siblings, and the binding prerequisite. The only mild gap is that pagination/first-page behavior is left entirely to the schema's cursor field rather than being reinforced.

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 every parameter including the pagination cursor and includeProjectChats default is already documented in the schema. The description only echoes the platform scoping and the optional query filter, adding no format or behavioral detail beyond the structured fields. Baseline 3 applies.

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 ("List chats") plus the scope ("for one platform in the bound browser") and the payload shape ("titles/ids, optional query"). The parenthetical distinguishes this lightweight listing from chats_get's "full payload", so an agent can pick correctly without opening a 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?

Explicitly frames the tool as the discovery entry point ("Prefer for discovery") and names three concrete alternatives with the selecting condition for each: projects_chats for in-project chats, chats_get for full payloads, chat_outline for turn indexes. It also states the prerequisite "Requires prior browsers_bind", which prevents a common ordering mistake.

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