Skip to main content
Glama
Sign In
Browser MCP

Browser MCP

by Agent360dk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_switch_tab

Switch to a specific browser tab by ID. Get tab IDs from browser_list_tabs or browser_get_new_tab. The other tools then act on that tab.

Instructions

Switch to a specific browser tab by ID. Get tab IDs from browser_list_tabs or browser_get_new_tab. The other tools then act on that tab. Chrome is not brought in front of the user: the tab is made active in its window, and visibility says whether the page is hidden behind other windows.

Input Schema

NameRequiredDescriptionDefault
tab_idYesTab ID to switch to
bring_to_frontNoAlso bring the Chrome window in front of the user. Takes the user's screen: only after the user agreed (browser_ask_user). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.30.2
    • addedInput schema / properties / bring_to_front
      Added value: +{
+  "description": "Also bring the Chrome window in front of the user. Takes the user's screen: only after the user agreed (browser_ask_user). Default false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / tab_id / description
      Previous value: -"Tab ID to activate"New value: +"Tab ID to switch to"
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that Chrome is not brought in front of the user, that the tab is made active within its window, and it decodes the 'visibility' status semantics. It omits error behavior for invalid tab IDs, but the side-effect profile is unusually well disclosed for an unannotated tool.

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?

Three tight sentences, front-loaded with the core action and ID sourcing before the behavioral nuance. Every sentence earns its place, though the final sentence about visibility is slightly dense.

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?

No output schema or annotations, so the description must carry the behavioral load, and it largely does—covering tab activation scope, the front-of-screen distinction, and ID provenance. Only the failure mode for an invalid or closed tab ID is left unaddressed.

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?

Schema coverage is 100% so the baseline is 3, but the description adds genuine meaning beyond the schema by distinguishing 'active in its window' from 'in front of the user' and explaining what visibility conveys about tab_id's effect.

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+resource ('Switch to a specific browser tab by ID') and immediately differentiates it from siblings by naming where IDs come from (browser_list_tabs, browser_get_new_tab) and clarifying that subsequent tools act on the switched tab.

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?

Gives clear context for when this tool is the right step (after listing/creating tabs, before other tab-scoped tools) and flags the consent prerequisite for bring_to_front via browser_ask_user. It stops short of an explicit 'do not use when...' exclusion, but the routing guidance is strong.

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