Skip to main content
Glama
Sign In
open-browser-control

open-browser-control

by smankoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_switch_tab

Switch to a specific browser tab by providing its tab ID, obtained from listing tabs, to navigate directly to the desired page.

Instructions

Switch to a specific browser tab by its ID.

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

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab ID to switch to (get IDs from browser_list_tabs)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral transparency. It fails to disclose what happens on invalid tab ID, whether it changes browser focus, or any side effects. This is a significant gap for a tool that mutates state.

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 a single, front-loaded sentence with no extraneous words. It efficiently conveys the core purpose and links to the parameter source.

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 simple one-parameter tool with no output schema, the description covers the essential purpose and parameter source. However, missing behavioral details (e.g., error handling) leave some incompleteness.

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 tabId parameter's schema description is complete (100% coverage), and the tool description adds value by directing users to browser_list_tabs for IDs. The description enhances understanding 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 action 'Switch to a specific browser tab by its ID,' which distinguishes it from siblings like browser_list_tabs (list) and browser_new_tab (create). The verb and resource are specific and unambiguous.

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

Usage Guidelines4/5

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

The description provides context by referencing browser_list_tabs for obtaining tab IDs, implying usage when a tab ID is available. However, it does not explicitly state when not to use this tool or mention alternatives.

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