Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

switch_tab

Activates a specific browser tab by ID and brings it to the foreground so actions target the correct tab.

Instructions

Switch to a specific tab (bring it to front)

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": {
      "tabId": "<tabId>"
    },
    "name": "switch_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does disclose that the tab is brought to the front, which implies a focus change, but says nothing about failure behavior for invalid tab IDs, whether other state changes, or what the call returns.

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?

A single short sentence with the action front-loaded and no filler. It is efficient, though the parenthetical could have been spent on parameter meaning instead.

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?

This is a simple one-parameter tool, so the description is nearly sufficient. However, with no annotations, no output schema, and no schema parameter documentation, the critical gap is how to obtain a valid tabId.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only says 'a specific tab'. It never explains whether tabId is an index, an ID returned by the tabs or open_tab tools, or any valid range, leaving an agent unable to source the value confidently.

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?

The description states a specific verb and resource ('Switch to a specific tab') and the parenthetical clarifies the effect ('bring it to front'). This clearly separates it from open_tab, close_tab, and tabs, though it does not name those siblings explicitly.

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?

There is no guidance on when to prefer this over alternatives such as open_tab or tabs, nor on preconditions like whether the tab must already exist. The agent must infer the usage context entirely.

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