camoufox-agent

browse_find

Read-only

Navigate to a URL and search its visible text, returning bounded context around each match so you can locate content on a page without extracting the full document.

Instructions

Navigate once, search visible text, and return bounded context matches.

Input Schema

Name	Required	Description	Default
`os`	No	Optional OS to spoof. Can be 'windows', 'macos', or 'linux'. If not specified, will rotate between all OS types.
`url`	Yes	The URL to navigate to. Must be a fully qualified http or https URL.
`args`	No	Additional browser command-line arguments to pass to the browser. Rejected unless CAMOUFOX_MCP_ALLOW_UNSAFE_OPTIONS=1; denied args are always rejected.
`geoip`	No	Automatically detect geolocation based on IP address.
`proxy`	No	Proxy configuration for routing browser traffic through an HTTP(S) proxy. Proxy servers are checked against the same local-network URL policy as page requests.
`query`	Yes	Visible text to search for on the page.
`locale`	No	Browser locale (e.g., 'en-US', 'fr-FR').
`window`	No	Set fixed window size [width, height] instead of random generation. An empty array [] is accepted and treated as if the window parameter was not specified.
`timeout`	No	Timeout in milliseconds for page load (5-300 seconds).
`headless`	No	Run browser in headless mode. Auto-detects best mode for environment if not specified.
`humanize`	No	Enable realistic cursor movements and human-like behavior for better stealth and anti-detection.
`selector`	No	Optional CSS selector to limit extraction to one matching element.
`viewport`	No	Custom viewport dimensions.
`emulation`	No	Context emulation for diagnosing how the page behaves under other conditions.
`maxMatches`	No	Maximum matches to return.
`block_webgl`	No	Block WebGL to prevent fingerprinting and tracking.
`block_images`	No	Block all images for faster loading, reduced bandwidth, and lightweight browsing.
`block_webrtc`	No	Block WebRTC entirely for enhanced privacy and stealth.
`contextChars`	No	Characters of surrounding visible text to return per match.
`disable_coop`	No	Disable Cross-Origin-Opener-Policy for sites that require it.
`enable_cache`	No	Cache pages, requests, etc. Uses more memory but improves performance when revisiting pages.
`waitStrategy`	No	Wait strategy for page load. Defaults to 'domcontentloaded'. 'load' waits for all resources, 'networkidle' waits for network activity to finish.	domcontentloaded
`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.
`exclude_addons`	No	List of default addons to exclude (e.g., ['ublock_origin']). Rejected unless CAMOUFOX_MCP_ALLOW_UNSAFE_OPTIONS=1.
`includeConsole`	No	Include bounded page console diagnostics in the JSON response.
`includeNetwork`	No	Include bounded network diagnostics in the JSON response.
`stealthProfile`	No	Convenience profile for common Camoufox browser settings. Explicit options override profile values.	normal
`firefox_user_prefs`	No	Custom Firefox user preferences to set. Rejected unless CAMOUFOX_MCP_ALLOW_UNSAFE_OPTIONS=1; denied prefs are always rejected.

Output Schema

Name	Required	Description	Default
`url`	Yes
`query`	Yes
`title`	No
`status`	No
`matches`	Yes
`message`	No
`selector`	No
`truncated`	Yes
`maxMatches`	Yes
`contentType`	No
`diagnostics`	No
`contextChars`	Yes
`challengeType`	No
`selectorFound`	Yes
`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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is clear. The description adds that matches are 'bounded' and navigation is a single pass, but it does not disclose important behavioral details such as CAPTCHA handling, wait strategies, stealth profiles, or what happens on navigation failure.

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 efficiently structured, though for a tool with 28 parameters it may be too terse to be maximally helpful.

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?

The tool is complex, with 28 parameters, nested objects, and multiple behavioral knobs, but it has an output schema and rich annotations. The description covers the core action but omits context about CAPTCHA policy, stealth profiles, blocking options, and timeout behavior, leaving it only minimally adequate for such a broad tool.

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 one of the 28 parameters is documented in the schema itself. The description adds no parameter-specific meaning beyond the general idea of searching visible text and returning bounded context, so the baseline 3 is appropriate.

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 names a specific compound action: navigate once, search visible text, and return bounded context matches. This clearly separates it from pure extraction or session-based tools, though it does not name any sibling alternative to differentiate against explicitly.

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?

The phrase 'Navigate once' implies a one-shot workflow, which hints at when to use it versus persistent session tools, but there is no explicit guidance on when not to use it or which siblings to prefer for extraction, snapshots, or repeated navigation.

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