Skip to main content
Glama

web_switch_tab

Activates a browser tab by its ID, bringing it to the front so AI agents can continue interacting with the correct page.

Instructions

Bring a tab to the front / make it active, by 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": {
      "target_id": "<target_id>"
    },
    "name": "web_switch_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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. It implies a UI focus/state change but says nothing about behavior when the id is unknown, whether the caller's other tab state is affected, or whether the operation is user-visible.

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 front-loaded sentence with no filler. The slash construction is slightly informal but the meaning lands immediately.

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 UI tool with no annotations and no output schema, the description covers the core action but leaves error behavior and id sourcing unexplained. Adequate minimum, not more.

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 0% for the single target_id field, so the schema contributes nothing beyond 'string'. The description adds that it is a tab identifier, but not its format or provenance (which listing tool supplies it).

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 concrete verb+resource: making a tab active/frontmost, and scopes it with 'by id'. It is distinguishable from siblings like web_tabs or web_new_tab, though the description never names them.

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 when-to-use guidance and no mention of alternatives or prerequisites (e.g., that the id must come from web_tabs, or how this differs from web_navigate/web_new_tab). 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.