Skip to main content
Glama
chrome-remote-debugging-mcp

chrome-remote-debugging-mcp

by danilin-em

navigate

Open a URL in a Chrome tab, creating a new tab when no tab ID is provided and returning the tab ID for later calls.

Instructions

Navigate a Chrome tab to url.

Opens a new tab when tab_id is omitted; pass the returned tab_id to later calls to keep working in it. Returns {"tab_id", "url", "frameId"} on success, {"error": ...} otherwise.

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": "navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
tab_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the important side effect that omitting tab_id creates a new tab, and it documents the success and error response shapes, which is valuable because no output schema exists. It does not say whether navigation waits for page load, what permissions or browser state are required, or what happens to unsaved state in the current tab.

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?

Three short sentences, front-loaded with the core action and followed by the lifecycle rule and return shape. No filler, though the return-shape sentence is dense and the backtick formatting adds visual noise without information.

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 two-parameter browser tool with no annotations and no output schema, the definition covers the essentials: the action, the tab-creation default, reuse of the returned identifier, and both success and error return shapes. Remaining gaps (load semantics, error categories) are modest for a tool of 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 0%, so the description must compensate for both parameters. It explains tab_id thoroughly — omit to create, pass the returned value to reuse — but says nothing about url beyond the name, leaving format expectations (scheme, absolute vs relative) undocumented.

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?

The description opens with a specific verb and resource ("Navigate a Chrome tab to url"), which is unambiguous and clearly distinct from sibling operations like list_tabs, close_tab, or evaluate. It stops short of naming an alternative, but the action itself is concrete enough that an agent can select it 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 guidance is limited to parameter-level behavior: omitting tab_id opens a new tab, and the returned tab_id should be reused for subsequent calls. That is genuinely useful lifecycle guidance, but there is no statement of when to use navigate versus browse, browse_act, or evaluate, and no exclusions or prerequisites.

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