Skip to main content
Glama

Continue after the person

browser_resume
Read-only

Waits for a person to complete sign-in, one-time code, 2FA, device approval, or CAPTCHA in the open pilotfish browser, then resumes once the page moves on.

Instructions

When a result says NEEDS A PERSON (a sign-in, a one-time code or 2FA, a device approval, a CAPTCHA), tell the user in your reply what the page needs and that the pilotfish browser window is open on it; when they have done it there (or right after asking), call this and carry on: it waits until the page has moved on, then returns it. BLOCKED and STOP mean the site cannot be continued that way.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_sNoDefault 300

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnly and non-destructive, so safety is covered; the description adds the important behavioral fact that the call blocks until the page has moved on, plus the human-in-the-loop prerequisite in the external browser window. It omits what happens when the timeout expires or the page never advances, which matters for a blocking tool.

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?

Front-loads the trigger condition, then the action, then the exclusion for BLOCKED/STOP, in roughly two dense sentences. Nothing is padding; every clause carries an instruction the agent needs.

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

Completeness5/5

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

No output schema exists, and the description tells the agent what the call yields (the page, once it has moved on) and what the state markers in prior results mean. For a one-parameter blocking resume tool with annotations covering safety, the only minor gap is timeout-expiry 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?

One optional parameter with 100% schema coverage (timeout_s, default 300, max 900). The description adds no extra meaning about how timeout interacts with the wait or what occurs on expiry, so the schema does all the work and the baseline 3 applies.

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 concrete verb and outcome: it waits until the page has moved on, then returns it, after a human has resolved a sign-in, 2FA, CAPTCHA, or device approval. The trigger (a result saying NEEDS A PERSON) makes it distinguishable from generic siblings like browser_wait, though it never names an alternative explicitly.

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

Usage Guidelines5/5

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

Gives explicit when-to-use: only after a result says NEEDS A PERSON and the user has acted in the pilotfish browser window. It also gives the negative case, stating that BLOCKED and STOP mean the site cannot be continued this way, and it instructs what to tell the user before calling.

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