Skip to main content
Glama

browser_attach_identity

Read-onlyIdempotent

Switch an open page to another browser identity: the page is reopened at its current address in that identity's own browser (its cookies and storage), under the same page_id. What was typed or loaded on the page is not kept. For a first navigation, pass identity_name to browser.open instead.

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": {
      "page_id": "<page_id>",
      "identity_name": "<identity_name>"
    },
    "name": "browser_attach_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
identity_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. Added
  7. Removed
  8. Added
  9. Removed
  10. First observed

TDQS

A4/5.0
Behavior2/5

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

The description is unusually candid that page state is discarded ('What was typed or loaded on the page is not kept'), which is exactly the kind of side effect an agent needs. However, this disclosure is in tension with the supplied annotations readOnlyHint=true and destructiveHint=false: reopening the page in a different browser context discards typed input and loaded content, which is an environment mutation. The description itself is informative, but the combined definition sends conflicting signals about safety.

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?

Three short sentences, front-loaded with the action and mechanism, then the side effect, then the alternative. Every sentence carries distinct information with no filler or repetition of the tool name.

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 small 3-parameter tool with no output schema, the description covers what it does, the state-loss consequence, and the sibling alternative, which is most of what an agent needs. Remaining gaps are minor: how to discover identity_name values and behavior when the identity or page is invalid.

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 description coverage is only 33% (only in_workspace is documented), so the description must compensate, and it largely does: it explains that identity_name selects the browser context whose cookies and storage are used, and clarifies page_id as the identifier preserved across the switch. The one undocumented-in-description parameter, in_workspace, is covered by its own schema description, so nothing critical is lost.

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 ('Switch an open page to another browser identity') and then explains the mechanism precisely: the page is reopened at its current address inside the target identity's own browser/storage under the same page_id. The closing sentence explicitly separates it from browser.open, so an agent can distinguish it from the sibling without opening either schema.

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 an explicit when-not with a named alternative: for a first navigation, pass identity_name to browser.open instead. Implicitly restricts usage to pages that are already open ('Switch an open page'). It does not say how to obtain a valid identity_name (e.g. via browser_list_identities or browser_create_identity) or what happens if the identity does not exist, but the core routing guidance is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.