Skip to main content
Glama
Sign In
chat-export-server

chat-export-server

by svergio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

projects_chats

Read-onlyIdempotent

List chats inside a specific project or container using a known containerId. Discover IDs with projects_list first and bind the browser before calling.

Instructions

List chats inside one project/container on the bound browser. Prefer over chats_list when scoped to a known containerId; use projects_list first to discover ids. Requires 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>",
      "containerId": "<containerId>"
    },
    "name": "projects_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax chats to return (1-100)
cursorNoOpaque pagination cursor; null/omit for first page
platformYesProvider id: chatgpt | grok | grok-x | claude | copilot | qwen | deepseek | perplexity
containerIdYesProject/container id from projects_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.4
    • addedInput schema / properties / containerId / description
      Added value: +"Project/container id from projects_list"
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque pagination cursor; null/omit for first page"
    • 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"
  2. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds non-obvious operational context: it acts on the 'bound browser' and requires browsers_bind first, which is a prerequisite the annotations cannot express. It does not discuss pagination behavior beyond what the cursor parameter already implies.

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, each doing distinct work: what it does, when to prefer it, and the prerequisite. The scoping constraint is front-loaded and there is no 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 a read-only paginated list tool with full schema coverage and a complete annotation set, the description covers purpose, routing, and prerequisites adequately; no output schema exists so return values need not be explained. The only minor gap is that pagination/termination behavior (what an empty cursor result means) is left entirely to the schema.

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%, including the platform enum, limit bounds, and cursor semantics, so the schema carries the parameter burden and baseline is 3. The description's mention of containerId only repeats what the schema already states ('Project/container id from projects_list'), adding no new syntax, defaults, or format detail.

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 exact scope ('inside one project/container on the bound browser'), and explicitly contrasts itself with chats_list. An agent can distinguish it from chats_list and projects_list 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 selection guidance ('Prefer over chats_list when scoped to a known containerId'), a discovery path ('use projects_list first to discover ids'), and a hard prerequisite ('Requires browsers_bind'). When-to-use, how-to-prepare, and dependency are all named.

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

Deploy Server

Other Tools