camoufox-agent

browse_session_navigate

Navigate an existing browser session to a specified URL and return extracted text, HTML, or metadata, with optional selectors, wait strategies, and CAPTCHA handling.

Instructions

Navigate an existing browser session.

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL to navigate to. Must be a fully qualified http or https URL.
`timeout`	No	Optional timeout override for this navigation.
`maxChars`	No	Maximum text or HTML characters to return.
`selector`	No	Optional CSS selector to limit extraction.
`sessionId`	Yes	Session ID returned by browse_session_start.
`outputMode`	No	Response content mode.	text
`waitStrategy`	No	Optional wait strategy override for this navigation.
`captchaPolicy`	No	Challenge handling policy. 'detect' reports signals, 'pause' returns state for human action, 'fail' returns an error, 'attempt' returns enhanced challenge metadata, interactive elements, a bounded screenshot, and a suggested strategy. When CAPTCHA_AUTONOMOUS=true, responses are marked for LLM-assisted handling and include provider-specific challengePlaybook context when known.

Output Schema

Name	Required	Description	Default
`url`	Yes
`html`	No
`text`	No
`title`	No
`status`	No
`message`	No
`maxChars`	Yes
`selector`	No
`expiresAt`	Yes
`sessionId`	Yes
`truncated`	Yes
`outputMode`	Yes
`contentType`	No
`diagnostics`	No
`challengeType`	No
`selectorFound`	No
`captchaIframes`	No
`captchaDetected`	No
`challengeSignals`	No
`challengeHandling`	No
`challengePlaybook`	No
`challengeProvider`	No
`suggestedStrategy`	No
`requiresUserAction`	No
`interactiveElements`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is partly covered. The description adds essentially nothing beyond 'navigate'—it does not mention that navigation may wait for page load, return page content, encounter CAPTCHAs, or affect session state.

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 a single front-loaded sentence with no wasted words. It is efficient, though its brevity leaves important behavioral context unstated.

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?

For an 8-parameter, open-world navigation tool with rich options for output mode, wait strategy, and CAPTCHA policy, the description is far too thin. The output schema covers return values, but the description should at least signal that navigation loads a URL and can invoke configurable waiting and challenge-handling behavior.

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 every parameter including url, timeout, maxChars, selector, sessionId, outputMode, waitStrategy, and captchaPolicy is documented in the schema. The description contributes no additional parameter meaning, which is acceptable at baseline 3 when the schema is thorough.

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 gives a specific verb and resource: 'Navigate an existing browser session.' The word 'existing' implicitly distinguishes it from browse_session_start, though it does not explicitly name siblings or clarify how it differs from tools like browse_session_action or browse_session_resume.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as browse_session_start or browse_session_action, nor any mention of prerequisites like needing a sessionId from browse_session_start. Usage is only implied by the phrase 'existing browser session.'

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