Skip to main content
Glama

browser_switch_tab

browser_switch_tab
Idempotent

Brings a Chrome tab to the front of its window so the user can see the active tab. Use it when the visible tab must match the one being controlled.

Instructions

Bring a tab to the front of its window. Screenshots work without this, but the user will see the tab change.

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_idYesChrome tab ID.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare idempotent=true and destructive=false but say nothing about user-visible effects; the description fills that gap by disclosing that the tab visibly changes for the user and that screenshots don't require it. It stops short of covering failure behavior when the tab belongs to another session, which the session_id schema partly addresses.

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 short sentences, purpose front-loaded, followed by the one behavioral fact an agent can't get elsewhere. Nothing is redundant or padded.

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 simple, fully-documented, three-parameter tab operation with no output schema, the description covers purpose and the key user-visible side effect. Slightly more on session-ownership failure modes would complete it, but the input schema already handles that via session_id.

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%, with tab_id, session_id, and session_name all documented in the schema itself, so the baseline is 3. The description adds no further meaning about any parameter beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Bring a tab to the front of its window'), which cleanly separates it from browser_list_tabs, browser_claim_tab, and browser_open. It doesn't explicitly name a sibling it is not, but the action is unmistakable 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 Guidelines3/5

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

'Screenshots work without this' is an implicit when-not, and the visibility note hints at when to use it (when the user should observe the tab change). However, there is no explicit statement of when to prefer it over browser_claim_tab or browser_open, nor any prerequisite guidance, so usage must be inferred.

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