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

chat-export-server

by svergio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

projects_list

Read-onlyIdempotent

List projects or folders on a supported AI platform through your logged-in Chrome browser. Use it to browse containers before fetching the chats inside one project.

Instructions

List projects/folders (containers) on a platform via the bound browser. Prefer this over containers_list (identical legacy alias). Use projects_chats for chats inside one project, chats_list for all chats. 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>"
    },
    "name": "projects_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax projects to return (1-100)
queryNoOptional name filter when the provider supports it
cursorNoOpaque pagination cursor; null/omit for first page
platformYesProvider id: chatgpt | grok | grok-x | claude | copilot | qwen | deepseek | perplexity

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.4
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque pagination cursor; null/omit for first page"
    • addedInput schema / properties / limit / description
      Added value: +"Max projects 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 name filter when the provider supports it"
  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 establish readOnly, idempotent, non-destructive, open-world behavior, so the description's main value-add is the 'via the bound browser' execution model and the browsers_bind prerequisite, both genuinely useful. It stops short of describing pagination behavior or what the cursor returns, which leaves a small gap for a paged list operation.

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 carrying distinct information: purpose, sibling routing, and prerequisite. Nothing is repeated from the schema 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, well-documented list tool with no output schema, the description covers purpose, alternatives, and the browser-binding prerequisite. Only the shape of results and pagination flow are left implicit, which is a minor omission given the complete parameter documentation.

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 range, cursor semantics, and the caveat that query filtering is provider-dependent. The description adds no parameter-level meaning beyond the implied platform scoping, so the 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 projects/folders (containers)') plus the mechanism ('via the bound browser'), and immediately differentiates itself from containers_list. An agent can tell exactly what this returns 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 Guidelines5/5

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

Explicitly routes the agent: prefer this over the identical legacy alias containers_list, use projects_chats for chats within a project, chats_list for all chats. It also names the hard prerequisite, browsers_bind, so the agent knows what must be done first.

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