chrome-bridge-mcp

by deng1986

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

end_google_ai_session

Export and close a Google AI conversation session, clearing the active session if it matches.

Instructions

End a Google AI conversation session: export it, close the Chrome tab, and clear the active session if it matches.

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

Input Schema

Name	Required	Description	Default
`sessionId`	No	Session id returned by start_google_ai_session. Defaults to the active session.
`closeTab`	No	Whether to close the Chrome tab. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Describes main actions but lacks disclosure of destructive behavior (closing tab may lose unsaved data) or side effects. No annotations exist to compensate. The 'if it matches' condition is vague.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded with purpose. Could be slightly clearer with separate actions, but no wasted words.

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?

Adequate for a simple tool with two optional params and no output schema. Missing edge cases (session mismatch, error handling) and doesn't restate defaults from 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 covers both parameters fully (100%), so baseline is 3. Description adds no extra meaning beyond the schema.

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 tool ends a Google AI session by exporting, closing the tab, and clearing the active session if it matches. It distinguishes from sibling tools like start_google_ai_session and continue_google_ai_session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives like continue_google_ai_session or export_google_ai_session. Does not mention prerequisites or when not to use it.

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