Skip to main content
Glama

Run search automation now

spur_run_search_automation
Destructive

Run an approved search automation now. Can spend credits/actions and enroll owners in outreach according to its settings. Inspect it with spur_manage_search_automation get first; confirm the exact run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "automation_id": "<automation_id>",
      "confirm": "<confirm>"
    },
    "name": "spur_run_search_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
automation_idYesAutomation id (UUID from a Spur list/search tool)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "const": true,
      +  "description": "Set to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "automation_id"
      -]New value: +[
      +  "automation_id",
      +  "confirm"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint, openWorldHint and non-idempotency, but the description goes further by naming the concrete consequences: spending credits/actions and enrolling owners in outreach. It also states the confirmation gate ("confirm the exact run"), which is real behavioral context an agent needs before firing a side-effecting run.

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?

Three short sentences, front-loaded with the action, then consequences, then the required pre-flight check. Nothing is padded and the ordering matches the order an agent should reason about the call.

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?

For a two-parameter, side-effecting tool with rich annotations and no output schema, the definition covers purpose, cost, side effects and the approval gate. Only the response/result shape and repeat-run behavior are unstated, and non-idempotency is already covered by annotations.

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% and the confirm parameter already carries a strong description about explicit approval, so the schema does the heavy lifting. The description restates the confirmation requirement but adds no new meaning for automation_id, which is the baseline-3 case.

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?

States a specific verb and resource ("Run an approved search automation now") and immediately scopes it with "approved," which distinguishes it from spur_create_search_automation and from the manage tool. An agent can tell what this does without opening the schema.

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?

Gives an explicit precondition sequence: inspect with spur_manage_search_automation get first, then confirm the exact run. It does not name when to prefer a sibling launcher such as spur_run_data_job or spur_control_table_run, but the guidance for this tool's own workflow is clear and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources