chat-export-server

Overview Schema Source Related Servers Discussions Admin

browsers_list

Read-onlyIdempotent

List Chrome profiles currently connected through the Chat Export extension bridge so you can pick a browserId before binding a session.

Instructions

List Chrome profiles currently connected through the Chat Export extension bridge. Use before browsers_bind to pick a browserId; use browsers_status for the already-bound session only.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Nov 11, 2026

TDQS

A4.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered without the description. The text adds useful scoping context that only live extension-bridge connections appear, but it says nothing about what a returned entry contains or what an empty list 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?

Two sentences, no filler. The purpose comes first and the routing guidance follows immediately, so an agent gets the decision-relevant information at the front.

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 zero-parameter read tool with no output schema, the definition is nearly complete on selection and safe invocation. The remaining gap is that it does not describe the fields of a listed profile beyond implying a browserId, which would matter when chaining into browsers_bind.

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?

The tool takes no parameters, so the schema baseline is 4. The description does mention picking a browserId from the results, which hints at the shape of the returned identifier without any parameter meaning to explain.

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 description names a specific verb and resource ("List Chrome profiles") plus a precise scope ("currently connected through the Chat Export extension bridge"), which immediately distinguishes it from the other browsers_* tools.

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?

It states exactly when to use it ("Use before browsers_bind to pick a browserId") and names the alternative for the other case ("use browsers_status for the already-bound session only"), which covers both the sequencing and the exclusion.

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