Skip to main content
Glama

edit_scout

Idempotent

Update an existing scout's query, schedule, webhook configuration, or status. Pause, resume, or archive scouts to control monitoring.

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
queryNo
statusNo
scout_idYes
is_publicNo
skip_emailNo
webhook_urlNo
output_fieldsNo
user_locationNo
user_timezoneNo
webhook_formatNo
output_intervalNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed40 schema fields changedv0.3.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / description
      Removed value: -"Input for editing an existing scout or changing its status."
    • 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"
    • 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: -"Updated run interval in seconds. Minimum 1800 (30 minutes)"
    • removedInput schema / properties / output_interval / minimum
      Removed value: -1800
    • removedInput schema / properties / output_interval / type
      Removed value: -"integer"
    • addedInput schema / properties / query / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / query / description
      Removed value: -"Updated monitoring query"
    • removedInput schema / properties / query / type
      Removed value: -"string"
    • removedInput schema / properties / scout_id / description
      Removed value: -"The scout's unique identifier (UUID)"
    • addedInput schema / properties / skip_email / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / skip_email / description
      Removed value: -"Updated email notification preference"
    • removedInput schema / properties / skip_email / type
      Removed value: -"boolean"
    • addedInput schema / properties / status / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "active",
      +      "paused",
      +      "done"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / status / description
      Removed value: -"Change scout status: 'active' (resume monitoring), 'paused' (stop temporarily), 'done' (archive permanently)"
    • removedInput schema / properties / status / enum
      Removed value: -[
      -  "active",
      -  "paused",
      -  "done"
      -]
    • removedInput schema / properties / status / type
      Removed value: -"string"
    • 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"
    • 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'"
    • 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: -"Updated HTTPS webhook URL. 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: -"EditScoutInput"New value: +"edit_scoutArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "result": {
      +      "title": "Result",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "title": "edit_scoutOutput",
      +  "type": "object"
      +}
  2. Changed2 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / output_fields / minItems
      Added value: +1
  3. First observedv0.2.9

TDQS

A3.5/5.0
Behavior3/5

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

Annotations indicate idempotency; description adds status behavior (pause/resume/archive) but lacks details on update semantics (partial vs full) or 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?

Two sentences efficiently convey purpose and a key usage pattern (status values) with no unnecessary words.

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?

The tool is complex (11 parameters, 1 required, various updates), but the description covers only a small subset of functionality, lacking details on optional parameters and update behavior.

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?

With 0% schema description coverage, the description only groups parameters vaguely (query, schedule, webhook) and fails to explain most of the 11 parameters (e.g., is_public, output_fields).

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 'Update an existing scout' with specific updatable aspects (query, schedule, webhook, status), distinguishing it from 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 Guidelines3/5

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

Implies use for updating scouts but provides no explicit guidance on when to use vs alternatives or prerequisite conditions.

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

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