Skip to main content
Glama

Stop or pause my job search

setJobSearchStatus
DestructiveIdempotent

Tell Clera the candidate is stepping back, the same as the not-looking page in Clera's emails. not_looking: not looking for now; matching stops until they turn their search back on (editPreferences appetite searching). not_now: pause until a date; returnOn (YYYY-MM-DD, today or later) is when Clera may check back in. The search does not restart on its own; to resume, editPreferences appetite searching. no_contact: never contact them again, on any channel. This revokes their consent everywhere and only Clera staff can undo it, so it asks for confirmation first; offer not_now or not_looking before it, and for deleting everything use deleteMyAccount. To only slow down rather than stop, use editPreferences appetite receptive. For email only, use setEmailSubscription.

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": {
      "choice": "<choice>"
    },
    "name": "setJobSearchStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
choiceYes
returnOnNoFor not_now: the date Clera may check back in, YYYY-MM-DD.
confirmNoContactNoOnly when your client cannot show the confirmation prompt: "confirm" once the candidate said yes to never being contacted again, "cancel" otherwise. Never set it on your own.

Output Schema

NameRequiredDescriptionDefault
choiceYes
recordedYes
returnOnYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, and the description adds substantial context beyond them: not_now does not auto-restart, no_contact revokes consent on all channels and can only be undone by Clera staff, and it triggers a confirmation prompt first. It also discloses that inputs and results are logged for usage tracking and support.

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?

Front-loads the core action, then a labeled line per mode, then the fallback/alternative routing and the logging note — each sentence carries distinct information. The telegraphic phrasing (e.g. 'editPreferences appetite searching') is dense but not padded.

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 a destructive, consent-revoking mutation, the description covers all three modes, the confirmation requirement, the irreversibility and who can undo it, the manual-resume caveat, and where to go for adjacent intents. An output schema exists, so return values need no explanation.

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

Parameters5/5

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

Goes well past the 67%-covered schema: it defines what each enum value means behaviorally, constrains returnOn to a date when Clera may check back in (and that it must be today or later, a constraint absent from the schema), and explains confirmNoContact is a fallback only when the client cannot render the confirmation prompt and must never be set unprompted.

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 (stopping/pausing the candidate's job search) and enumerates the three mutually exclusive modes (not_looking, not_now, no_contact) with a one-line gloss of each. An agent can distinguish this from setEmailSubscription or editPreferences 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 Guidelines5/5

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

Explicitly routes between alternatives: use editPreferences appetite receptive to only slow down, setEmailSubscription for email-only, deleteMyAccount to delete everything, and offer not_now or not_looking before escalating to no_contact. It also states the resume path (editPreferences appetite searching) for both stop modes.

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