Skip to main content
Glama
shaun0927

OpenChrome

by shaun0927
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

navigate

Navigate to a URL, go forward, or go back in Chrome. Supports stealth mode for anti-bot pages and headed mode to bypass CDN blocking.

Instructions

Navigate to URL or go forward/back. Omit tabId for new tab.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTab ID. Omit for new tab
urlYesURL, "forward", or "back"
workerIdNoWorker ID for parallel ops. Default: default
taskIdNoTask id when routing through a task-scoped browser lane.
laneIdNoTask-scoped browser lane id. When supplied with taskId, navigate uses/records the lane-owned target.
stealthNoCDP-free mode: opens tab via Chrome debug API without CDP attachment during page load. Use for Cloudflare Turnstile or similar anti-bot pages. CDP attaches after page settles.
stealthSettleMsNoHow long to wait (ms) before attaching CDP in stealth mode. Default: 8000. Range: 1000-30000.
autoFallbackNoAuto-retry with stealth when CDN/WAF block is detected (access-denied, bot-check, captcha). Default: true. Set false to disable.
headedNoForce navigation in headed (non-headless) Chrome. Bypasses CDN/TLS-level blocking by using a real Chrome user-agent and TLS fingerprint. Requires a display. Default: false.
profileDirectoryNoChrome profile directory name (e.g., "Profile 1"). Use list_profiles to see available profiles. Launches a separate Chrome instance for each profile. If omitted, uses the server default. Cannot be combined with workerId.
recallNoOverride OPENCHROME_AUTO_RECALL for this call. true forces domain skill injection; false suppresses it even when the flag is on.
capture_artifactNoWhen true, stage a replay artifact navigation step for oc_skill_record after a successful URL navigation. Default false is a strict no-op.

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Annotations indicate mutability (readOnlyHint=false), and the description adds context about opening new tabs. Consistent and sufficient given annotation coverage.

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?

The description is front-loaded and concise, fitting in one sentence. Could be slightly more detailed without being verbose.

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

Completeness3/5

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

Given 12 parameters and no output schema, the description is minimal. It lacks details on return values, failure modes, or post-navigation state, which is expected for a simple tool but could be improved.

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?

With 100% schema coverage, baseline is 3. The description adds value by summarizing the core behavior of tabId ('Omit for new tab') and concisely covering url types.

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 description 'Navigate to URL or go forward/back' provides a specific verb and resource, clearly distinguishing from siblings like page_reload or tabs_create.

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 hint 'Omit tabId for new tab' gives context for one parameter, but lacks explicit when-to-use vs alternatives like page_reload or forward/back in history.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shaun0927/openchrome'

If you have feedback or need assistance with the MCP directory API, please join our Discord server