Skip to main content
Glama

Change a search

updateRoleSearch
DestructiveIdempotent

Change a Search's title, criteria or schedule, or pause or resume it. Only whoever started it or a team owner can change it. Changes apply from the next run.

criteria replaces the whole list (up to 5, each { id, text }); keep the ids of criteria you keep, from getRoleSearch. cadence is off, daily or weekly; weekly runs on weekday (0 = Sunday). sendHour is the hour in the company's time zone. maxNew caps new people per run. includeOutside also searches outside Clera, which uses more credits. Tell the user what will change and get a yes before calling.

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": {
      "roleSearchId": "<roleSearchId>"
    },
    "name": "updateRoleSearch"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
titleNo
maxNewNo
pausedNo
cadenceNo
weekdayNo
criteriaNo
sendHourNo
roleSearchIdYes
skipWeekendsNo
includeOutsideNo

Output Schema

NameRequiredDescriptionDefault
idYes
jobIdYes
titleYes
countsYes
promptYes
statusYes
newCountYes
roleNameYes
scheduleYes
canManageYes
createdAtYes
expiresAtYes
lastRunAtYes
nextRunAtYes
runNumberYes
requestedByYes
qualityFloorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description supplies the material behavior behind that: criteria replaces the whole list rather than merging, changes only apply from the next run, and includeOutside consumes more credits. The permission model and the note that inputs and results are recorded for support add non-obvious operational context found nowhere 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?

Three tight paragraphs ordered by importance: what changes, the permission and confirmation gate, then per-parameter semantics. Dense but nearly every clause carries information; the privacy/recording sentence is boilerplate that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter mutating tool this is well covered: authorization, replace-vs-merge semantics, timing of effect, cost implications, and the confirmation requirement are all present. An output schema exists, so the absence of return-value documentation is not a gap.

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 schema description coverage at 9% across 11 parameters, the description carries most of the burden and mostly delivers: criteria shape and the rule to reuse ids from getRoleSearch, cadence values, weekday numbering anchored at Sunday, sendHour interpreted in the company time zone, and maxNew semantics. It leaves skipWeekends, title constraints and paused behavior unexplained, so it is strong but not exhaustive.

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 opening sentence gives a specific verb and resource ('Change a Search') and enumerates the mutable surface (title, criteria, schedule, pause/resume). That distinguishes it cleanly from getRoleSearch, createRoleSearch and deleteRoleSearch without needing their schemas.

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 precondition ('Only whoever started it or a team owner can change it') and a procedural gate ('Tell the user what will change and get a yes before calling'), which is real when-to-use guidance. It does not name a sibling alternative or say when to prefer a different tool, so it falls short of a 5.

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