Yutori MCP

Official

Overview Schema Related Servers Score Discussions

run_browsing_task

Run a one-time browser automation task to perform actions on a webpage like a human. Receive a task ID to poll for results, enabling data extraction or form submissions from any starting URL.

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

Name	Required	Description	Default
`task`	Yes
`browser`	No
`max_steps`	No
`start_url`	Yes
`webhook_url`	No
`require_auth`	No
`output_fields`	No
`webhook_format`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed30 schema fields changedv0.3.1Jul 6, 2026

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

removedInput schema / description

Removed value: -"Input for running a one-time browsing task.\n\nThe Browsing API enables automation of browser-based workflows.\nAn AI agent runs its own cloud browser and operates it like a person -\nclicking, typing, scrolling, and navigating for you. Examples:\n- Fill forms on websites\n- Extract structured data from complex web pages\n- Automate multi-step workflows that require authentication"

addedInput schema / properties / browser / anyOf

Added value: +[
+  {
+    "enum": [
+      "cloud",
+      "local"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / browser / description

Removed value: -"Where 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."

removedInput schema / properties / browser / enum
```
Removed value: -[
-  "cloud",
-  "local"
-]
```
removedInput schema / properties / browser / type
```
Removed value: -"string"
```

addedInput schema / properties / max_steps / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / max_steps / description

Removed value: -"Maximum number of browser actions (1-100). Default: 25"

removedInput schema / properties / max_steps / maximum
```
Removed value: -100
```
removedInput schema / properties / max_steps / minimum
```
Removed value: -1
```
removedInput schema / properties / max_steps / type
```
Removed value: -"integer"
```

addedInput schema / properties / output_fields / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / output_fields / description

Removed value: -"Optional: 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)."

removedInput schema / properties / output_fields / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / output_fields / minItems
```
Removed value: -1
```
removedInput schema / properties / output_fields / type
```
Removed value: -"array"
```

addedInput schema / properties / require_auth / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / require_auth / description

Removed value: -"If true, use an auth-optimized cloud browser provider for login flows. Only applies when browser is 'cloud' (default)."

removedInput schema / properties / require_auth / type
```
Removed value: -"boolean"
```

removedInput schema / properties / start_url / description

Removed value: -"The URL where the navigator should begin. Example: 'https://yutori.com'"

removedInput schema / properties / task / description

Removed value: -"Natural 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'"

addedInput schema / properties / webhook_format / anyOf

Added value: +[
+  {
+    "enum": [
+      "scout",
+      "slack",
+      "zapier"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / webhook_format / description

Removed value: -"Webhook payload format: 'scout' (default), 'slack', or 'zapier'"

removedInput schema / properties / webhook_format / enum

Removed value: -[
-  "scout",
-  "slack",
-  "zapier"
-]

removedInput schema / properties / webhook_format / type
```
Removed value: -"string"
```

addedInput schema / properties / webhook_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / webhook_url / description

Removed value: -"HTTPS URL to receive webhook notification when task completes. Must use https://."

removedInput schema / properties / webhook_url / type
```
Removed value: -"string"
```

changedInput schema / title

Previous value: -"BrowsingTaskInput"New value: +"run_browsing_taskArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "run_browsing_taskOutput",
+  "type": "object"
+}

Changed2 schema fields changedv0.3.0Jun 14, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / output_fields / minItems
```
Added value: +1
```
First observedv0.2.9May 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It mentions the agent 'operates it like a person' and returns a task_id, but it does not disclose whether the tool is destructive, requires authentication, has rate limits, or what the scope of 'browsing' entails (e.g., navigation, form filling, scraping). This leaves significant behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (3 sentences) and front-loads the purpose. However, it sacrifices completeness for brevity, omitting critical parameter details and usage context. It is not overly verbose, but the conciseness is at the expense of utility.

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

Completeness2/5

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

Given 8 parameters (2 required), the presence of an output schema, and many sibling tools, the description is incomplete. It fails to explain how to use webhooks, polling, authentication, or output_fields. It also does not differentiate from the similar sibling run_research_task, leaving the agent without sufficient context for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only touches on 'task' (via example) and 'browser' (hint for local), but ignores the other 6 parameters (start_url, max_steps, webhook_url, require_auth, output_fields, webhook_format). No details on data types, constraints, or semantics beyond what the schema already shows.

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?

The description clearly states the tool executes a one-time web browsing task and uses a navigator agent that operates a browser like a person. It returns a task_id for polling, which defines the resource and action. However, it does not explicitly differentiate from sibling tools like run_research_task, so it loses some clarity for distinction.

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 gives an example ('list employees') and a usage hint for setting browser='local' to use the desktop app with logged-in sessions, which implies when this mode is appropriate. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., run_research_task, create_scout) and does not mention when not to use it.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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