camoufox-agent

browse_session_resume

Resume a paused browser session after human action and return the current page state, visible text, and interactive elements for continued automation.

Instructions

Resume a paused session after human action and return current state.

Input Schema

Name	Required	Description
`timeout`	No	Timeout in milliseconds for the resume wait.
`maxChars`	No	Maximum visible text and ARIA snapshot characters to return.
`selector`	No	Optional CSS selector to limit snapshot extraction.
`sessionId`	Yes	Session ID returned by browse_session_start.
`maxElements`	No	Maximum interactive elements to return.
`waitStrategy`	No	Optional load state to wait for before reading the session.
`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
`text`	Yes
`title`	No
`status`	No
`message`	No
`elements`	Yes
`maxChars`	Yes
`selector`	No
`expiresAt`	Yes
`sessionId`	Yes
`contentType`	No
`diagnostics`	No
`maxElements`	Yes
`ariaSnapshot`	No
`challengeType`	No
`selectorFound`	Yes
`textTruncated`	Yes
`captchaIframes`	No
`captchaDetected`	No
`challengeSignals`	No
`ariaSnapshotError`	No
`challengeHandling`	No
`challengePlaybook`	No
`challengeProvider`	No
`elementsTruncated`	Yes
`suggestedStrategy`	No
`requiresUserAction`	No
`interactiveElements`	No
`ariaSnapshotTruncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 29, 2026

TDQS

A4/5.0

Behavior3/5

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

With annotations already declaring readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, the description adds useful context that this happens after human action and returns current state. However, it does not explain the wait behavior, failure modes, or what resuming actually changes in the session.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, and the key condition and outcome are front-loaded. Every phrase contributes to understanding when and why to call the tool.

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

Completeness4/5

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

The description covers the trigger and outcome, while the rich input schema and output schema handle parameters and return values. It is complete enough for invocation, though it could say more about blocking semantics or what happens if the human action never occurs.

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 timeout, captchaPolicy, and waitStrategy is already documented in the schema. The description adds no parameter-level meaning beyond the structured fields, so baseline 3 applies.

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 states a specific verb and resource: resume a paused session. It also scopes the action to after human action and states that current state is returned, making the purpose immediately clear.

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?

It gives a clear usage condition: use when a session was paused and a human has acted. It does not name alternative tools such as browse_session_start or browse_session_action, nor does it state when not to use it, so it stops short of full routing guidance.

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