chrome-bridge-mcp

by deng1986

Overview Schema Source Related Servers Discussions Admin

export_google_ai_session

Export a Google AI conversation session to Markdown for project reports. Defaults to the active session.

Instructions

Export a persisted Google AI conversation session to Markdown in the project reports directory. Defaults to the active session.

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

Input Schema

Name	Required	Description	Default
`sessionId`	No	Session id returned by start_google_ai_session. Defaults to the active session.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It fails to mention whether the directory is created automatically, what the filename is, whether overwrites occur, what is returned (e.g., path), or error handling for missing session. The phrase 'persisted session' is ambiguous regarding state requirements.

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?

The description is a single, front-loaded sentence with no redundant words. It efficiently conveys the core action, target format, and default behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (1 optional param, no output schema), the description is partially complete but lacks behavioral details like success indication, output handling, and failure modes. It minimally covers the essential action but leaves agent guessing about post-export behavior.

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% for the single parameter sessionId. The description adds no new information beyond the schema's 'Defaults to the active session.' Baseline of 3 is appropriate as schema covers the parameter fully.

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 clearly states the verb 'export' and the resource 'persisted Google AI conversation session' to Markdown format in a specific directory. It differentiates from sibling tools like read_google_ai_session and google_ai_read by specifying the output format and destination.

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 implies usage by noting it defaults to the active session, providing context on when to omit sessionId. However, it does not explicitly state when to use this tool versus alternatives (e.g., read_google_ai_session) or what prerequisites exist (e.g., session must be persisted).

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