Skip to main content
Glama

Tabs

browser_tabs

List open tabs with the current one marked, and switch to another tab by ID to make it active and return its snapshot.

Instructions

List the open tabs (the current one is marked). switch_to makes another tab current and returns its snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
switch_toNoTab id to work in from now on, e.g. "t2"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description is consistent, explaining that switch_to mutates the current tab and returns its snapshot. It adds useful context beyond the annotations, though it doesn't say what happens to the previously current tab or how the marking is represented.

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 short sentences, front-loaded with the listing behavior and immediately followed by the switch behavior. No wasted wording.

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?

With no output schema, the description carries the return-value burden and does mention the snapshot returned by switch_to. It is nearly complete for a one-optional-parameter tool, missing only detail on the snapshot's form.

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 meaning: switch_to not only selects a tab but also returns that tab's snapshot, which the schema's "Tab id to work in from now on" does not convey.

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 and resource ("List the open tabs") and adds the dual behavior of switch_to. It is clearly distinguishable from siblings like browser_snapshot or browser_navigate, though it does not name any alternative explicitly.

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?

The description implies when switch_to is relevant (to make another tab current) but gives no explicit when-to-use/when-not guidance or named alternatives among the many browser_* siblings.

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