camoufox-agent

browse_links

Read-only

Navigates to a specified URL and returns only visible, navigable links, with optional CSS selector and link limit.

Instructions

Navigate once and return only visible navigable links.

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.
`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.
`maxLinks`	No	Maximum links to return.
`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.
`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.
`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
`links`	Yes
`title`	No
`status`	No
`message`	No
`maxLinks`	Yes
`selector`	No
`truncated`	Yes
`contentType`	No
`diagnostics`	No
`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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful filtering semantics—'visible' and 'navigable'—and 'once' suggests no persisted session, but it omits pagination behavior, whether links are deduplicated or absolutized, and what happens if the page load fails.

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?

It is a single front-loaded sentence with zero waste, and the most important constraint (visible navigable links only) appears immediately. It does not pad or bury the purpose.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a 26-parameter browser navigation tool with complex stealth/proxy/environment options, a one-sentence description leaves meaningful behavioral gaps around session lifecycle, link filtering, and failure handling.

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 the detailed 26-parameter schema already does the heavy lifting. The description adds no parameter-specific meaning—nothing about maxLinks, selector, waitStrategy, or whether stealth/proxy settings affect the returned links—so 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 states a specific verb+resource: navigate and return visible navigable links. It implies a one-shot action unlike session tools, but never names a sibling or explicitly distinguishes itself from browse, browse_extract, or browse_snapshot.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is mentioned. An agent must infer that this is for link discovery rather than for page inspection, extraction of other content, or persistent sessions.

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