Skip to main content
Glama

Add an Autopilot search

addAutopilotSearch

Saves a job board search to the candidate's Autopilot, with the filters searchJobs takes (at least one). While it is on, Clera runs it three times a day and fills applications from it. Refused once 3 are saved. Only when the candidate asked for it.

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

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": {
      "filters": "<filters>"
    },
    "name": "addAutopilotSearch"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOnly a name the candidate gave it; otherwise Clera names it.
enabledNo
filtersYes
emailAlertsNoWhile the search is off: email its new listings once a day.

Output Schema

NameRequiredDescriptionDefault
statusYes
searchIdYes
searchesYes
nextRunAtYes
tailorDocumentsYes
reviewBeforeSubmitYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only say readOnly=false, openWorld=true, idempotent=false, destructive=false), the description discloses the actual ongoing behavior: Clera runs the saved search three times a day and fills applications from it. It also states the 3-search cap, the consent requirement, and an explicit data-recording notice, none of which appear in structured fields.

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?

Four short sentences, each carrying distinct information (action, automation cadence, cap, consent), with the core action front-loaded. The trailing privacy/data-recording sentence is boilerplate but small and separated from the operational content.

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 nested-schema mutation with an output schema already covering return values, the description supplies the missing behavioral picture: cadence, cap, consent gating, and data handling. The only real gap is how to modify or disable an existing Autopilot search, which is left to siblings.

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 50% and the description compensates partially by defining the required `filters` semantics through the searchJobs reference and the 'at least one' minimum. It adds nothing about `enabled`, `emailAlerts`, or the defaults/behavior of the remaining parameters, leaving half the surface to the schema.

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 opens with a specific verb+resource ('Saves a job board search to the candidate's Autopilot') and anchors the input shape by pointing at the sibling that shares its filters ('the filters searchJobs takes'). An agent can distinguish this from editAutopilotSearch or removeAutopilotSearch without opening any 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?

It states a hard consent condition ('Only when the candidate asked for it') and a capacity limit ('Refused once 3 are saved'), which is exactly the guidance an agent needs before calling. It does not name editAutopilotSearch as the alternative for changing an existing search, so the routing guidance stops just short of complete.

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