Public Browser

run_plan

Reduce multiple round trips by batching browser actions into a single server-side call. Manage complex flows with variables, conditions, and error strategies.

Instructions

Batch the next 2+ known actions (click, type, scroll, view_page chains) here instead of N separate calls: a sequence of tool steps, executed server-side in one call. Variables via vars and saveAs ($name), conditions (if), suspend/resume to ask the agent mid-plan, and errorStrategy abort | continue | capture_image.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`vars`	No	Initial variables, available as $name
`steps`	No	Tool steps to run in order
`resume`	No	Resume a suspended plan
`errorStrategy`	No	abort stops at the first error; continue runs all steps; capture_image screenshots, then aborts	abort

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.0.0Sep 24, 2026

removedInput schema / properties / parallel

Removed value: -{
-  "description": "Tab groups to run in parallel",
-  "items": {
-    "properties": {
-      "steps": {
-        "description": "Steps for this tab",
-        "items": {
-          "$ref": "#/properties/steps/items"
-        },
-        "type": "array"
-      },
-      "tab": {
-        "description": "Tab ID (targetId)",
-        "type": "string"
-      }
-    },
-    "required": [
-      "tab",
-      "steps"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

removedInput schema / properties / use_operator

Removed value: -{
-  "default": false,
-  "description": "Operator mode (rule engine + micro-LLM); needs the executeOperator hook",
-  "type": "boolean"
-}

Changed24 schema fields changedv2.10.5Sep 4, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / errorStrategy

Added value: +{
+  "default": "abort",
+  "description": "abort stops at the first error; continue runs all steps; capture_image screenshots, then aborts",
+  "enum": [
+    "abort",
+    "continue",
+    "capture_image"
+  ],
+  "type": "string"
+}

changedInput schema / properties / parallel / description

Previous value: -"Array of tab groups to execute in parallel across tabs."New value: +"Tab groups to run in parallel"

removedInput schema / properties / parallel / items / additionalProperties
```
Removed value: -false
```
changedInput schema / properties / parallel / items / properties / steps / description
```
Previous value: -"Steps to execute on this tab"New value: +"Steps for this tab"
```

changedInput schema / properties / parallel / items / properties / tab / description

Previous value: -"Tab ID (targetId) to execute steps on"New value: +"Tab ID (targetId)"

removedInput schema / properties / resume / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / resume / description

Previous value: -"Resume a previously suspended plan."New value: +"Resume a suspended plan"

changedInput schema / properties / resume / properties / answer / description

Previous value: -"Agent's answer to the suspend question"New value: +"Answer to the suspend question"

changedInput schema / properties / resume / properties / planId / description

Previous value: -"ID of the suspended plan to resume"New value: +"ID of the suspended plan"

changedInput schema / properties / steps / description

Previous value: -"Array of tool steps to execute sequentially."New value: +"Tool steps to run in order"

removedInput schema / properties / steps / items / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / steps / items / properties / if / description

Previous value: -"Condition expression — step runs only if true. Use $varName for variables. Example: \"$pageTitle === 'Login'\""New value: +"Run the step only if this expression is true, e.g. \"$pageTitle === 'Login'\""

changedInput schema / properties / steps / items / properties / params / description

Previous value: -"Parameters for the tool. Use $varName for variable substitution."New value: +"Tool parameters; $name substitutes a variable"

changedInput schema / properties / steps / items / properties / saveAs / description

Previous value: -"Save step result as variable (accessible via $name in later steps)"New value: +"Save the result as $name for later steps"

removedInput schema / properties / steps / items / properties / suspend / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / steps / items / properties / suspend / description

Previous value: -"Suspend plan at this step to ask the agent a question"New value: +"Pause here to ask the agent a question"

changedInput schema / properties / steps / items / properties / suspend / properties / condition / description

Previous value: -"Condition expression — suspend AFTER step if true. Uses $varName syntax."New value: +"Suspend after the step if this $-expression is true"

changedInput schema / properties / steps / items / properties / suspend / properties / context / description

Previous value: -"Context to include: 'capture_image' captures the page"New value: +"capture_image: attach a screenshot"

changedInput schema / properties / steps / items / properties / suspend / properties / question / description
```
Previous value: -"Question to ask the agent when suspending"New value: +"Question for the agent"
```

changedInput schema / properties / steps / items / properties / tool / description

Previous value: -"Tool name to execute (e.g. 'click', 'type', 'press_key', 'navigate', 'scroll')"New value: +"Tool name"

changedInput schema / properties / use_operator / description

Previous value: -"Operator mode (rule engine + Micro-LLM). Requires the executeOperator hook to be registered."New value: +"Operator mode (rule engine + micro-LLM); needs the executeOperator hook"

addedInput schema / properties / vars

Added value: +{
+  "additionalProperties": {},
+  "description": "Initial variables, available as $name",
+  "type": "object"
+}

First observedv2.7.0Jun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It transparently describes server-side execution, variable handling via vars and saveAs, conditions, suspend/resume for mid-plan interaction, and errorStrategy options. It does not detail side effects (which depend on the underlying tools) but provides a clear picture of the tool's control-flow behavior.

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, dense paragraph that front-loads the core purpose ('Batch the next 2+ known actions...') and then enumerates the key features efficiently. Every clause adds information, and there is no filler or repetition.

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 tool is complex with nested objects and multiple control-flow options. The description covers the major features (variables, conditions, suspend/resume, error strategy) and the schema fills in structural details. It could be more explicit about when to use suspend or error strategies, but the combination of description and schema is sufficient for an agent to understand the tool's role and capabilities.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds conceptual meaning beyond the schema by explaining how the parameters work together: variables available as $name, saveAs for later steps, if conditions, suspend/resume, and errorStrategy choices. This synthesis helps an agent understand the batching workflow, elevating it above a bare parameter list.

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 clearly states the tool's function: batching 2+ known actions into a single server-side call. It explicitly contrasts with N separate calls, which differentiates it from individual action tools. The resource is well-defined as a sequence of tool steps, and the purpose is unmistakable.

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?

The description implies when to use it: when you have 2+ known actions to execute. It mentions 'instead of N separate calls', which is a clear usage directive. However, it does not explicitly name sibling tools like batch_evaluate or exclude scenarios where individual calls are preferable, leaving some room for inference.

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

run_plan

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools