WebRun Browser Automation

Run browser task

browser_task

Destructive

Execute a browser automation task in a real Chrome browser running in a WebRun cloud environment (docs.webrun.ai). Creates a session, runs the task, and auto-terminates. Best for simple one-off tasks that no saved workflow covers. May navigate, fill forms, and submit data on third-party websites as the task requires. Do NOT use this to run or test a saved workflow — use trigger_workflow instead: only a workflow run carries the workflow's own rules, tracking and memory, so a session run will behave differently. If the user says "run it", "run it once", "test it" or "try it" about a workflow, that means trigger_workflow, not this tool.

Input Schema

TableJSON Schema

Name	Required	Description
`files`	No	Optional file IDs to attach: ids returned by POST /files/upload, or any file already in one of the user's environment catalogs (GET /environments/:id/files). Max 5 files.
`model`	No	Optional model name or profile key (from global config). Falls back to the configured default.
`proxy`	No	Proxy configuration. WebRun-managed: { source: "WebRun", country: "GB" }. Custom: { source: "custom", type: "http"\|"socks", host, port, username?, password? }. Omit for no proxy. Social/messaging automation (WhatsApp, Telegram, Instagram, Facebook, X, LinkedIn, TikTok): prefer country = the country the user is in right now — recommend it and confirm the country with them first; a mismatch is the usual cause of refused logins and sessions that log out repeatedly.
`debugC`	No	Enable debug mode on the instance (default: false)
`prompt`	Yes	Task description in natural language
`secrets`	No	Domain-matched secrets [{match, fields}] passed to instance (not stored)
`webhook`	No	Webhook configuration for task completion notification
`policyId`	No	Policy ID to apply automation guardrails (domain restrictions, capability controls, LLM role). Optional.
`timezone`	No	IANA timezone name for the session, e.g. "America/New_York", "Europe/London", "Asia/Tokyo". Date/time-sensitive instructions (e.g. "tomorrow morning", "today", "in 2 hours") are interpreted in this timezone. When omitted, follows the WebRun proxy country if one is set (e.g. country "de" → Europe/Berlin); otherwise the browser default.
`outputType`	No	Response format (default: text)
`maxDuration`	No	Max duration in minutes (default: 20, max: 60)
`startingUrl`	No	Optional starting URL
`outputSchema`	No	JSON Schema for structured output (required if outputType is structured_json)
`environmentId`	No	Environment ID for persistent profile session. Use list_environments to find available IDs. Without this, a disposable instance is used.
`reach_out_mode`	No	Controls proactive chat-platform messages (Telegram/WhatsApp/Slack/Discord/Teams) to bot users on the same environment. Default: "off" — no messages are sent unless this is set explicitly. "guardrail_only" forwards guardrail prompts (CAPTCHA/2FA/verification) to chat when the API caller is offline. "full" also forwards the task result on completion. Each bot user additionally filters by their own reachOutMode preference.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Task output payload (instance-authored shape)
`type`	No	Result type, e.g. 'task_completed', 'task_failed', 'guardrail_trigger'
`error`	No
`status`	No	Present on guardrail results: 'awaiting_input'
`taskId`	No
`message`	No
`pending`	No	True when the task is still running — poll get_task_status
`success`	No
`sessionId`	No
`environment`	No
`liveViewURL`	No	Page for watching the run live, present while it is still running or awaiting input. The only URL here that is safe to show a user or open in a browser.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / timezone / description

Previous value: -"IANA timezone name for the session, e.g. \"America/New_York\", \"Europe/London\", \"Asia/Tokyo\". Date/time-sensitive instructions (e.g. \"tomorrow morning\", \"today\", \"in 2 hours\") are interpreted in this timezone. Defaults to \"UTC\" when omitted."New value: +"IANA timezone name for the session, e.g. \"America/New_York\", \"Europe/London\", \"Asia/Tokyo\". Date/time-sensitive instructions (e.g. \"tomorrow morning\", \"today\", \"in 2 hours\") are interpreted in this timezone. When omitted, follows the WebRun proxy country if one is set (e.g. country \"de\" → Europe/Berlin); otherwise the browser default."

Changed1 schema field changedSep 6, 2026

changedInput schema / properties / files / description

Previous value: -"Optional file IDs to attach (from /files/upload). Max 5 files."New value: +"Optional file IDs to attach: ids returned by POST /files/upload, or any file already in one of the user's environment catalogs (GET /environments/:id/files). Max 5 files."

Changed1 schema field changedSep 2, 2026

changedInput schema / properties / proxy / description

Previous value: -"Proxy configuration. WebRun-managed: { source: \"WebRun\", country: \"GB\" }. Custom: { source: \"custom\", type: \"http\"|\"socks\", host, port, username?, password? }. Omit for no proxy."New value: +"Proxy configuration. WebRun-managed: { source: \"WebRun\", country: \"GB\" }. Custom: { source: \"custom\", type: \"http\"|\"socks\", host, port, username?, password? }. Omit for no proxy. Social/messaging automation (WhatsApp, Telegram, Instagram, Facebook, X, LinkedIn, TikTok): prefer country = the country the user is in right now — recommend it and confirm the country with them first; a mismatch is the usual cause of refused logins and sessions that log out repeatedly."

Changed1 schema field changedAug 26, 2026

addedOutput schema / properties / liveViewURL

Added value: +{
+  "description": "Page for watching the run live, present while it is still running or awaiting input. The only URL here that is safe to show a user or open in a browser.",
+  "type": "string"
+}

Changed1 schema field changedAug 17, 2026

changedInput schema / properties / maxDuration / description

Previous value: -"Max duration in minutes (default: 5)"New value: +"Max duration in minutes (default: 20, max: 60)"

Changed1 schema field changedAug 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Task outcome envelope: a completion (success/type/data), a pending marker (poll get_task_status), or an awaiting_input guardrail. `data` is the task output; its shape is task-defined (freeform text or the caller-supplied structured schema).",
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "Task output payload (instance-authored shape)",
+      "type": "object"
+    },
+    "environment": {
+      "properties": {
+        "environmentId": {
+          "type": "string"
+        },
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "pending": {
+      "description": "True when the task is still running — poll get_task_status",
+      "type": "boolean"
+    },
+    "sessionId": {
+      "type": "string"
+    },
+    "status": {
+      "description": "Present on guardrail results: 'awaiting_input'",
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "taskId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "description": "Result type, e.g. 'task_completed', 'task_failed', 'guardrail_trigger'",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Discloses that it creates a session, runs the task, and auto-terminates, and warns about side effects on third-party websites. Annotations already cover destructive and openWorld hints, but the description adds context about session lifecycle and behavioral differences from workflows.

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?

Well-structured and front-loaded: starts with core action, then lifecycle, then usage guidance and exclusion. Every sentence contributes value, with no filler or redundancy.

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?

Given the tool's complexity (15 params, nested objects, output schema) and rich schema, the description covers the key usage context and lifecycle. It could explicitly state the return format, but that is partially addressed by outputType/outputSchema parameters and sibling tools for status.

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 coverage is 100%, so all 15 parameters have detailed descriptions in the schema. The tool description itself does not add additional parameter-specific details beyond the schema, which is the baseline for high coverage.

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?

Clearly states the tool executes browser automation tasks in a real Chrome browser via WebRun, and explicitly differentiates from trigger_workflow. The verb 'execute' plus resource 'browser task' is specific and unambiguous.

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?

Explicitly states it is best for one-off tasks not covered by workflows, and explicitly warns against using it for saved workflows, naming trigger_workflow as the alternative. Also clarifies that phrases like 'run it' about a workflow should route to trigger_workflow.

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

All WebRun Browser Automation tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?