Skip to main content
Glama

Open a page in Chrome

open_in_browser

Opens an http/https URL in your own Chrome profile so you can view dashboards, builds, or edited pages already signed in with existing cookies.

Instructions

Open a URL in the user's own Google Chrome so they can look at it themselves (a dashboard, a failing build, a page you just edited). It opens in the Chrome profile that holds that site's cookies, so the page is already logged in. Only http/https URLs.

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": {
      "url": "<url>"
    },
    "name": "open_in_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to open (http or https).
profileNoChrome profile directory to use instead, e.g. 'Default' or 'Profile 1'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only=false, destructive=false, open-world=true, but the description adds non-obvious behavior: it launches on the user's machine and uses the Chrome profile holding the site's cookies, so the page is pre-authenticated. That cookie/session implication is exactly the kind of side-effect context annotations cannot convey. It stops short of describing what happens if no profile matches or Chrome is not running.

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 tight sentences: purpose first, behavioral payoff second, hard constraint last. Every clause earns its place and there is no restating of the title.

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 two well-documented parameters, full annotations, and no output schema, the remaining burden is light and the description covers the essentials. Only an edge-case note (no matching profile, browser unavailable) is missing, which is minor at this complexity.

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 description coverage is 100%, so both parameters are already documented. The description implies the default profile selection rule ('the profile that holds that site's cookies') without naming the profile parameter or explaining precedence when it is supplied. Baseline 3 applies when the schema carries the detail.

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: opening a URL in the user's own Google Chrome. The parenthetical examples (dashboard, failing build, edited page) pin down the concrete use case, and nothing about it is ambiguous.

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?

The phrase 'so they can look at it themselves' clearly signals the situation that selects this tool (hand something visual to the human), and 'Only http/https URLs' sets a usage constraint. There is no explicit when-not or named alternative, but the siblings are unrelated auth tools, so there is little to disambiguate.

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