camoufox-agent

browse_network_summary

Read-only

Navigate to a URL once and return a bounded summary of network diagnostics, including failed requests, to help diagnose page load and connectivity issues.

Instructions

Navigate once and return a bounded network diagnostic summary.

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.
`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.
`maxFailures`	No	Maximum failed requests to include in the summary.
`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
`title`	No
`failed`	Yes
`status`	No
`blocked`	Yes
`message`	No
`requests`	Yes
`truncated`	Yes
`contentType`	No
`topFailures`	Yes
`statusCounts`	Yes
`challengeType`	No
`captchaIframes`	No
`captchaDetected`	No
`challengeSignals`	No
`challengeHandling`	No
`challengePlaybook`	No
`challengeProvider`	No
`suggestedStrategy`	No
`requiresUserAction`	No
`resourceTypeCounts`	Yes
`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 readOnly, non-destructive, open-world and non-idempotent, so safety is covered elsewhere. The description adds only the word 'bounded' and no insight into the heavyweight behaviors exposed by its 25 parameters (proxy routing, stealth profile, captcha policy, emulation, timeouts), which is a real gap for a tool with this many behavioral knobs.

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?

A single front-loaded sentence with no filler, and the navigation-plus-summary shape is stated immediately. It is efficient, though arguably under-specified rather than wasteful.

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 a 25-parameter tool with an output schema and rich annotations, a one-sentence description leaves too much implicit: how the summary is shaped, why the stealth/proxy/captcha options matter here, and how it relates to the diagnostic and session siblings. The output schema excuses return-value detail, but not the missing routing context.

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% and every parameter, including nested proxy/emulation fields and enums, is documented inline, so the schema carries the semantics. The description adds nothing about parameters, but the baseline of 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Navigate once') plus a distinct output ('bounded network diagnostic summary'), which separates it from a plain browse/snapshot tool. It does not, however, name or contrast with the closest siblings such as browse_diagnose or browse_session_navigate, so the agent must infer the boundary.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. 'Navigate once' mildly implies a one-shot, no-session workflow, but nothing tells the agent when to pick this over browse_diagnose, browse_inspect or browse_session_navigate.

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