Skip to main content
Glama

tab_switch

Switch to a specific browser tab by ID, make it the active tab in its window, and bring that window to the front. Use a tab ID from tab_list or tab_read.

Instructions

Show a tab in the user's browser: make it the active tab of its window and bring that window to the front. Take the tab id from tab_list.

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

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It clearly discloses the visible side effect of switching focus to the tab and its window, but it does not state failure behavior for invalid or missing tab ids, platform or browser requirements, or whether the operation returns anything. The core effect is transparent, but important edge behavior is left implicit.

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 tightly written sentences with no wasted words. The primary effect is front-loaded, followed by the practical instruction for obtaining the tab id.

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 one-parameter focus tool with complete schema coverage and no output schema, the description covers the essential action and its visible effect. It could be strengthened with error or platform behavior, but it is otherwise complete enough for an agent to call it correctly.

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 coverage is 100%, so the single tabId parameter is already fully documented, including that it comes from tab_list or tab_read and defaults to the active tab. The description adds only 'Take the tab id from tab_list,' which is narrower than the schema and adds little meaning beyond it. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Show a tab' and then precisely defines the effect as making it the active tab of its window and bringing that window to the front. This is more specific than a generic activate call and is distinguishable from sibling tools such as tab_list and tab_read based on the stated action.

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 implied by the action: use this when the user needs a tab made visible or active. The only routing guidance is 'Take the tab id from tab_list,' which addresses where to get the parameter rather than when to choose this tool over alternatives. No explicit when-not or alternative-selection guidance is provided.

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