WebRun Browser Automation

Create browser session

create_session

Destructive

Create a persistent session in a real Chrome browser running in a WebRun cloud environment (docs.webrun.ai), for multi-step interactive work. Returns a sessionId for subsequent commands. With an initial task the browser may act on third-party websites immediately. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Session mode (default: default)
`task`	No	Initial task configuration
`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.
`debugC`	No	Enable debug mode on the instance (default: false)
`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. Defaults to "UTC" when omitted.
`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
`taskId`	No	Task ID when an initial task was provided
`message`	No
`sessionId`	Yes	Session ID for subsequent commands
`streaming`	No	Endpoints for watching the running browser. Only liveViewURL is a web page — the other two are machine endpoints on a non-standard port.
`environment`	No	Environment this session is bound to, when one was requested

TDQS

A4.7/5.0

Behavior5/5

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

Annotations mark the tool as destructive and open-world, and the description adds important behavioral context: the browser may act on third-party websites immediately, the session is persistent, and it returns a sessionId for subsequent commands. This goes beyond the annotations by explaining what actually happens when an initial task is provided.

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?

The description is three concise sentences with no filler. It front-loads the core purpose, then covers return value and side effects, and ends with the critical workflow-vs-session distinction. Every sentence earns its place.

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?

Given the complexity of the tool, the description covers the essential decision boundary (session vs workflow), the operational environment, the immediate external side-effect potential, and the return value. An output schema is present, so return structure does not need to be explained further.

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 has a rich description in the schema, so the baseline applies. The tool description does not add parameter-level meaning, but it does not need to because the schema already covers parameter semantics fully.

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 uses a specific verb and resource: create a persistent session in a real Chrome browser in a WebRun cloud environment, for multi-step interactive work. It also names the key sibling alternative (trigger_workflow), so an agent can distinguish a session from a workflow run.

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?

The description explicitly states when to use the tool (multi-step interactive work) and gives a clear exclusion: do not use it for saved workflows; use trigger_workflow instead. It explains why, because a workflow run carries its own rules, tracking, and memory, making session runs behave differently.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool targets a distinct resource or action: browser_task vs create_session differentiate one-off vs persistent sessions, trigger_workflow is explicitly separated from generic task execution, and the pause/resume/stop/terminate actions are scoped to either agents or session tasks. There is no overlap where an agent could mis-select between tools.

Naming Consistency4/5

The vast majority follow a consistent verb_noun pattern (create_, list_, get_, pause_, resume_, stop_, terminate_, trigger_, update_, send_). Two tools deviate: browser_task (noun_verb) and guardrail_response (noun), but these are minor and still readable within the overall convention.

Tool Count4/5

21 tools is on the higher end but justified by the domain covering three distinct resource types (sessions, workflows, agents) plus environments and status/guardrail handling. It is slightly heavy but each tool serves a clear purpose without redundancy.

Completeness3/5

Core lifecycle operations are covered for sessions (create, list, terminate, send task, pause/resume/stop task) and workflows (create, get, list, update, trigger). However, there are notable gaps: no delete operations for workflows or agents (only pause/resume for agents, and no delete_workflow), and no dedicated get_agent detail endpoint. These omissions could force agents to work around missing functionality.

Resources

Need Help?