Yutori MCP

Official

Overview Schema Source Related Servers Discussions Admin

create_scout

Set up continuous web monitoring for any query and receive alerts when relevant changes occur. Track specific topics, prices, or news over time.

Instructions

Create a monitoring scout for continuous web monitoring. Scouts track changes relevant to a query and alert you. Examples: 'news about Yutori', 'H100 pricing below $1.50'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`is_public`	No
`skip_email`	No
`webhook_url`	No
`output_fields`	No
`user_location`	No
`user_timezone`	No
`webhook_format`	No
`output_interval`	No
`start_timestamp`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed36 schema fields changedv0.3.1Jul 6, 2026

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

removedInput schema / description

Removed value: -"Input for creating a new monitoring scout.\n\nScouts enable continuous monitoring of the web at a configurable schedule\nfor tracking any changes relevant to a query. Example queries:\n- \"anytime a startup in SF announces seed funding\"\n- \"when H100 pricing per hour drops below $1.50\"\n- \"latest news and product updates about Yutori\""

addedInput schema / properties / is_public / anyOf

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

removedInput schema / properties / is_public / description

Removed value: -"Whether scout results are publicly accessible"

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

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: ['headline', 'summary', 'url']. If omitted, returns human-readable text. For complex schemas, call the Yutori REST API directly (see example at: https://docs.yutori.com/reference/scouts-create#using-scheduling-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 / output_interval / anyOf

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

removedInput schema / properties / output_interval / description

Removed value: -"Seconds between scout runs. Minimum 1800 (30 minutes). Default: 86400 (daily)"

removedInput schema / properties / output_interval / minimum
```
Removed value: -1800
```
removedInput schema / properties / output_interval / type
```
Removed value: -"integer"
```

removedInput schema / properties / query / description

Removed value: -"Natural language description of what to monitor. Examples: 'Tell me about the latest news, product updates, or announcements about Yutori', 'when H100 pricing per hour drops below $1.50', 'anytime a startup in SF announces seed funding'"

addedInput schema / properties / skip_email / anyOf

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

removedInput schema / properties / skip_email / description

Removed value: -"If true, skip email notifications (useful with webhooks)"

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

addedInput schema / properties / start_timestamp / anyOf

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

removedInput schema / properties / start_timestamp / description

Removed value: -"Unix timestamp for when monitoring should start (0 = immediately)"

removedInput schema / properties / start_timestamp / type
```
Removed value: -"integer"
```

addedInput schema / properties / user_location / anyOf

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

removedInput schema / properties / user_location / description

Removed value: -"User location for geo-relevant searches. Format: 'city, region, country'"

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

addedInput schema / properties / user_timezone / anyOf

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

removedInput schema / properties / user_timezone / description

Removed value: -"Timezone for scheduling. Example: 'America/New_York'. Default: 'America/Los_Angeles'"

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

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 notifications when updates are available. Must use https://. Confirm the URL with the user before setting."

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

changedInput schema / title

Previous value: -"CreateScoutInput"New value: +"create_scoutArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "create_scoutOutput",
+  "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

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses core behavior (creates scout, monitors, alerts) but omits details like required permissions, reversibility, or side effects. Adequate but not thorough.

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 short, front-loaded with action and purpose, and includes examples. Efficient but could be improved by adding parameter guidance without losing conciseness.

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 10 parameters and a complex domain, the description is incomplete. It neglects to explain optional parameters like webhook_url, output_fields, or start_timestamp, and doesn't mention the output schema. Significant gaps.

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

Parameters1/5

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

Schema coverage is 0%; description fails to explain any of the 10 parameters, including the required 'query'. No additional meaning provided beyond the schema. Parameter documentation is completely absent.

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 verb 'Create', resource 'scout', and purpose 'continuous web monitoring, track changes, alert'. Examples clarify use cases. It distinguishes from siblings like delete_scout and list_scouts.

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 implies usage for setting up new monitoring scouts but lacks explicit when-to-use, when-not-to-use, or alternatives. No guidance relative to siblings beyond the context.

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

Deploy Server