Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

switch_to_tab

Activates and focuses a specified Google Chrome tab by its tab ID, bringing the target tab to the foreground for browser control tasks.

Instructions

Activate/focus a tab in Google Chrome

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_to_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab ID to activate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and largely restates the name. It does convey the effect (activation/focus), but says nothing about failure behavior for an unknown tabId, whether the browser window is raised, or whether other tabs' state is affected.

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?

One short sentence, front-loaded with the action and resource, with no redundant phrasing. Nothing to trim.

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?

For a one-parameter, no-output-schema tool the description is mostly sufficient, but it omits the error case (nonexistent or closed tab) and any note about focus semantics across multiple windows. Adequate but with a clear gap.

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% and the single parameter tabId is documented in the schema itself. The description adds no meaning beyond that, so baseline 3 applies.

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 (activate/focus) and resource (a tab in Google Chrome), which cleanly separates it from siblings like new_tab, close_tab, and list_tabs. It doesn't explicitly name those siblings, but the action is unambiguous.

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?

Usage is only implied: it's the tool to call when an agent needs to bring an existing tab into focus. There is no explicit statement of when to prefer it over alternatives such as new_tab or get_current_tab, nor any prerequisite (e.g., the tab must already exist).

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