Skip to main content
Glama

browser_claim_tab

browser_claim_tab
Idempotent

Claim an existing browser tab this session does not own, such as a page the user already has open, and add it to the session's tab group so other sessions are refused access.

Instructions

Take over a tab this session does not own yet, for example a page the user already had open. The tab joins the session group unless you pass group: false, and other sessions are refused it from then on.

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": {
      "tab_id": "<tab_id>"
    },
    "name": "browser_claim_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
tab_idYesChrome tab ID.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare mutation, non-destructiveness and idempotency, but say nothing about group membership or ownership contention. The description fills exactly that gap: the tab joins the session group by default, group: false opts out, and other sessions are refused the tab afterward. It does not state what happens if the caller claims a tab it already owns or what a refusal looks like, so it falls short of a 5.

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 sentences, zero filler. The core action is stated first, the default behavior and its override second, and the exclusivity consequence last, which is the right order for an agent deciding whether to call it.

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 mutation tool with no output schema, the description covers purpose, default side effect, opt-out, and cross-session exclusivity. What is missing is failure/conflict behavior (claiming a tab another session already holds) and whether re-claiming an owned tab is a no-op, which matters given the idempotent hint.

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 75%, and the one undocumented parameter, group, is precisely the one the description explains (defaults on, opt out with false). That compensates for the schema gap rather than repeating it. tab_id and session_name are already well documented in the schema, so no extra credit is warranted there.

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?

"Take over a tab this session does not own yet" gives a specific verb (take over) plus a resource (tab) with a scope qualifier that separates it from operating on an already-owned tab. The example ("a page the user already had open") grounds the abstraction. It stops short of naming the near-miss sibling (browser_switch_tab) that handles tabs the session already holds, so differentiation is inferable rather than stated.

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 phrase "this session does not own yet" plus the user-had-it-open example implies the trigger condition, and "unless you pass group: false" gives a branch. But there is no explicit when-not guidance and no named alternative for the common adjacent case of switching to a tab you already own, so the agent has to infer the boundary.

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