Skip to main content
Glama

run_browsing_task

Execute a one-time web browsing task using an AI agent that operates a browser like a person—filling forms, extracting data, and automating multi-step workflows.

Instructions

Execute a one-time web browsing task. The navigator agent runs a browser and operates it like a person. Returns a task_id for polling. Example: 'list employees'. Set browser='local' to use the desktop app with the user's logged-in sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesNatural language instruction for the navigator agent. Examples: 'Give me a list of all employees (names and titles) of Yutori', 'Fill out the contact form with my information', 'Extract product prices from this page'
start_urlYesThe URL where the navigator should begin. Example: 'https://yutori.com'
max_stepsNoMaximum number of browser actions (1-100). Default: 25
require_authNoIf true, use an auth-optimized cloud browser provider for login flows. Only applies when browser is 'cloud' (default).
browserNoWhere to run the browser. 'cloud' (default) uses Yutori's cloud browser. 'local' uses Yutori Local with the user's logged-in sessions on the desktop. Requires the desktop app to be running.
output_fieldsNoOptional: Extract structured data as an array of objects with these field names. Example: ['name', 'title', 'email']. If omitted, returns human-readable text. For complex schemas, call the Yutori REST API directly (see example at: https://docs.yutori.com/reference/browsing-create#using-webhooks-and-a-structured-output-schema).
webhook_urlNoHTTPS URL to receive webhook notification when task completes. Must use https://.
webhook_formatNoWebhook payload format: 'scout' (default), 'slack', or 'zapier'
Behavior3/5

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

No annotations are provided, so the description must bear the full burden. It discloses that the tool runs a browser like a person and returns a task_id for polling, but lacks details on error handling, idempotency, or security implications of the 'local' browser option.

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 concise with three sentences plus an example. It front-loads the main purpose and avoids fluff, though it could be slightly more efficient by integrating the example into the first sentence.

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

Completeness3/5

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

For a tool with no output schema, the description mentions the return value as a task_id for polling but does not specify the format or direct users to the polling endpoint. Parameters are well-covered by schema, so the description is adequate but not fully comprehensive.

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 the schema already documents all parameters. The description only adds minor context for the 'browser' parameter, thus adding limited value beyond the schema.

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 executes a one-time web browsing task using a navigator agent, with a specific verb ('execute') and resource ('web browsing task'). It includes an example and distinguishes from sibling tools by emphasizing the one-time nature.

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

Usage Guidelines3/5

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

The description provides minimal guidance on when to use this tool vs. alternatives. While it mentions the 'browser' parameter option, it does not compare with siblings like 'run_research_task' or 'create_scout'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yutori-ai/yutori-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server