Skip to main content
Glama

Change an Autopilot search

editAutopilotSearch

Changes one saved Autopilot search by searchId from readAutopilot: on or off, name, filters (the whole set) or email alerts. Without searchId, enabled turns every search off, or back on. Only when the candidate asked for it.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "editAutopilotSearch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
enabledNo
filtersNo
searchIdNoThe search's searchId from readAutopilot.
emailAlertsNo

Output Schema

NameRequiredDescriptionDefault
statusYes
searchesYes
nextRunAtYes
tailorDocumentsYes
reviewBeforeSubmitYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, so the description's added value is the warning that filters are replaced as "the whole set" (an overwrite, not a merge) and the non-obvious fallback that omitting searchId toggles every saved search. It also discloses that inputs and results are recorded, which annotations do not convey.

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?

Two dense, front-loaded sentences cover the field set, the bulk-mode edge case, and the consent condition with no filler. The separate privacy sentence is boilerplate but is a required disclosure rather than wasted prose.

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 mutation tool with a large nested filter schema and an output schema, the description covers the essentials: addressing, replace-vs-merge semantics, the global toggle path, and the consent precondition. Nothing critical for correct invocation appears to be missing.

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

Parameters4/5

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

With only 20% top-level schema coverage, the description carries the load and does: it explains searchId's origin, that enabled with no searchId is a global switch, and that filters replaces the entire filter set. The deeply nested filters object is documented in the schema itself, which the description sensibly does not duplicate.

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 ("Changes one saved Autopilot search") and enumerates the exact mutable fields: on/off, name, filters, email alerts. It also pins the addressing key ("by searchId from readAutopilot"), which cleanly separates it from creation/removal siblings and from the broader editAutopilot.

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 a strong consent gate ("Only when the candidate asked for it") and explains the alternate bulk path when searchId is omitted. It does not explicitly contrast against editAutopilot or addAutopilotSearch, but the when/when-not conditions are clear from the text itself.

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