Skip to main content
Glama

browser_save_session

Save the sign-in of an OPEN page into the browser identity the page was opened with (browser.open with identity), the same as a person's "I'm logged in, save session" button. Without it a sign-in made in a browser.open page is lost when the page closes, and everything that reads the identity (channels.reconnect, integrations) keeps the old session. Call it ONLY after checking the page shows the signed-in state (a logged-out page would replace a working session), before closing it. Refused when the page was opened without an identity, when the identity is not active or expired, or when the page is not signed in to the identity's own site. For a PENDING identity, pass the page_id browser.handoff(prepare=true, confirm_agent_sign_in=true) returned, after you signed in there: the identity becomes active and that window closes (the page_id stops working; continue with browser.open(identity=...)). Nothing secret is returned. Needs the member, admin or owner role.

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>"
    },
    "name": "browser_save_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYespage_id of the open, signed-in page (from browser.open with identity, or from browser.handoff with prepare=true).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page_id / description
      Previous value: -"page_id of the open, signed-in page (from browser.open with identity)."New value: +"page_id of the open, signed-in page (from browser.open with identity, or from browser.handoff with prepare=true)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations (which only say non-read-only, non-idempotent, non-destructive) to disclose the consequence of omission (session lost on close, channels.reconnect and integrations keep stale state), four distinct refusal conditions, role requirements (member/admin/owner), and that no secret is returned. The handoff side effect — the window closes and page_id stops working — is a behavior an agent could not infer elsewhere.

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?

Front-loaded with the action and the failure consequence, then the guardrail, then the edge case — a logical order with no filler sentences. It is dense as a single paragraph, but every clause carries operational information, so length is largely earned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation-adjacent tool with no output schema, it covers trigger conditions, refusal cases, permissions, side effects, and confirms nothing sensitive is returned. An agent has everything needed to call it correctly and to recover when it is refused.

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 page_id and in_workspace are already documented; the description still adds the meaningful origin distinction (from browser.open with identity vs. from browser.handoff prepare=true) and that the handoff-derived page_id becomes unusable afterward. in_workspace is not addressed in the description, but its schema text is self-sufficient.

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?

The first sentence gives a specific verb and resource ('Save the sign-in of an OPEN page into the browser identity') and anchors it to the concrete analogy of a person's 'save session' button. It clearly separates this from browser.open and browser.handoff, which are named in the same breath.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when: after the page shows the signed-in state, before closing it; explicit when-not: never on a logged-out page because it would replace a working session. The pending-identity path routes the agent to browser.handoff(prepare=true, confirm_agent_sign_in=true) and then back to browser.open, so the alternative workflow is spelled out.

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.