Skip to main content
Glama

edit_scout

Idempotent

Update an existing monitoring scout's configuration: modify query, schedule, webhook settings, or change status to pause, resume, or archive.

Instructions

Update an existing scout's query, schedule, webhook configuration, or status. Use status='paused' to pause, 'active' to resume, or 'done' to archive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scout_idYesThe scout's unique identifier (UUID)
statusNoChange scout status: 'active' (resume monitoring), 'paused' (stop temporarily), 'done' (archive permanently)
queryNoUpdated monitoring query
output_intervalNoUpdated run interval in seconds. Minimum 1800 (30 minutes)
webhook_urlNoUpdated HTTPS webhook URL. Must use https://. Confirm the URL with the user before setting.
webhook_formatNoWebhook payload format: 'scout' (default), 'slack', or 'zapier'
output_fieldsNoOptional: 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
skip_emailNoUpdated email notification preference
user_timezoneNoTimezone for scheduling. Example: 'America/New_York'
user_locationNoUser location for geo-relevant searches
is_publicNoWhether scout results are publicly accessible
Behavior3/5

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

Annotations provide idempotentHint: true, and the description does not contradict this. However, it adds minimal behavioral context beyond what the schema already provides, such as not mentioning immediate effect or any side effects.

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 two sentences, front-loading the purpose and then providing specific status usage. No unnecessary words.

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 11 optional parameters fully documented in schema, the description covers core usage. It lacks guidance on output or return value, but this is an edit tool where output is typically a confirmation.

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 the baseline is 3. The description adds little extra meaning beyond the schema; the status usage is already detailed in the enum description.

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 'Update' and the resource 'existing scout', listing specific fields (query, schedule, webhook configuration, status). This distinguishes it from sibling tools like create_scout and delete_scout.

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

Usage Guidelines4/5

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

The description provides explicit usage for status values ('active', 'paused', 'done') and their effects. However, it does not contrast with alternatives like delete_scout or explain when not to use this tool.

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