Skip to main content
Glama
Sign In
cdp-bridge

cdp-bridge

by Unagi-cq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

browser_switch_tab

Switch the active browser tab for MCP interactions without altering the visible Chrome tab.

Instructions

Switch the active MCP browser tab without changing the visible Chrome tab.

Args: tab_id: The tab ID to switch to (from browser_get_tabs).

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": {
      "tab_id": "<tab_id>"
    },
    "name": "browser_switch_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.21

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the behavioral burden. It explicitly states that the Chrome tab is not changed, which is a key behavioral trait. However, it does not mention error handling or side effects for invalid tab_id.

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 two sentences plus an Args section, with no wasted words. It is front-loaded with the core purpose and efficiently provides parameter guidance.

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?

Given the tool simplicity (1 param), no annotations, and an output schema, the description covers the main behavior and parameter origin. It could mention failure modes or constraints, but overall it is complete enough.

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 input schema has 0% description coverage, so the description must add meaning. It explains that tab_id comes from browser_get_tabs, which adds context beyond the schema. Could be more specific about format but is sufficient.

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 it switches the active MCP browser tab without changing the visible Chrome tab. This is a specific verb+resource and distinguishes from sibling tools like browser_focus_tab.

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

Usage Guidelines3/5

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

The description tells where to get tab_id (from browser_get_tabs) but does not explicitly guide when to use or avoid this tool compared to alternatives like browser_focus_tab. Usage context is implied but not clearly stated.

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