Skip to main content
Glama
Sign In
sandboxed-browser-mcp

sandboxed-browser-mcp

by smkamranqadri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Back

browser_back

Steps back one page in the browser tab history and returns the previous page as text; if no earlier page exists, it returns an error and stays put.

Instructions

Steps back one page in the tab's history and returns that page as text. When the tab has no earlier page, it answers with an error and stays put.

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_back"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoWhich browser profile (a separate signed-in session) to use. Leave it out for the default one; name another only when the user's task names it. Profiles: default.default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / profile
      Added value: +{
+  "default": "default",
+  "description": "Which browser profile (a separate signed-in session) to use. Leave it out for the default one; name another only when the user's task names it. Profiles: default.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true; the description adds genuine behavioral context beyond them by disclosing that the page is returned as text and that on no earlier history it errors and 'stays put', i.e. no state change on failure. It does not describe whether history entries are consumed or how the text is produced, so a 5 is not warranted.

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?

Two short sentences, front-loaded with the action and the return value, followed by the failure mode. No filler, though the second sentence could be marginally tighter.

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

Completeness2/5

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

With only 1 optional parameter and no output schema, the definition is nearly complete: it states the action, the return (page as text) and the failure behavior. The only gap is that the error/stay-put case is not tied to any recovery path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single optional 'profile' parameter is fully documented in the schema, so baseline 3 applies. The description adds nothing about profile selection or defaults.

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?

Specific verb plus resource: 'Steps back one page in the tab's history' plus the return ('as text'). An agent can immediately distinguish this from browser_navigate or browser_click without opening the schema.

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?

Usage is implied by the navigation semantics (return to the previous page in this tab), and the no-history failure case is stated. However, it offers no explicit guidance on when to prefer this over browser_navigate for going back, nor any exclusion conditions.

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