Skip to main content
Glama

Withdraw from a hiring process

withdrawFromProcess
Destructive

Pull the candidate out of a hiring process that is already running (status process: submitted to the company or interviewing), the same as withdraw on the dashboard's Matches cards. Take the opportunityId from listMyPipeline.

It can't be undone here: the row moves to withdrawn, and Clera follows up with the candidate about what changed. Only call it when the candidate has said they want out of this specific role, and pass their reason in their own words when they gave one. A like or pass on a role that isn't in process yet goes to undoMatchDecision or declineMatch instead.

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": {
      "opportunityId": "<opportunityId>"
    },
    "name": "withdrawFromProcess"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy the candidate is withdrawing, in their own words. Leave it out when they didn't say.
opportunityIdYesThe opportunityId of a process row from listMyPipeline.
confirmWithdrawNoOnly when your client cannot show the confirmation prompt: "withdraw" once the candidate has said yes to leaving this specific process, "cancel" otherwise. Never set it on your own.

Output Schema

NameRequiredDescriptionDefault
positionYes
withdrawnYes
companyNameYes
opportunityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the crucial consequence: the change cannot be undone here, the row moves to withdrawn, and Clera follows up with the candidate. It also discloses a data-handling trait (inputs and results are privately recorded for usage tracking and support) that no structured field conveys.

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 paragraphs ordered by importance: what it does, irreversibility, when to call plus alternatives, then the privacy notice. Nearly every sentence carries decision-relevant information; the usage-tracking sentence is boilerplate but is the only non-operational text.

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, non-idempotent mutation, the definition covers trigger conditions, irreversibility, downstream effects, identifier sourcing, and sibling alternatives, and an output schema exists so return values need not be described. Nothing an agent needs in order to call this safely on behalf of a candidate is 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?

Schema coverage is 100% and the schema descriptions already cover omitting reason and not setting confirmWithdraw unaided, so the description mostly reinforces rather than adds. It does add workflow-level meaning by tying opportunityId to listMyPipeline and by framing reason as the candidate's own words tied to the withdrawal decision, which helps an agent fill the fields correctly.

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?

Uses a specific verb and object ("Pull the candidate out of a hiring process that is already running") and bounds the scope to rows in submitted/interviewing status. It also names the UI equivalent ("withdraw on the dashboard's Matches cards") and points at listMyPipeline for the identifier, so an agent knows exactly what action this performs.

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?

Gives an explicit precondition ("Only call it when the candidate has said they want out of this specific role") and routes the out-of-scope case to concrete alternatives: undoMatchDecision or declineMatch for a like/pass on a role not in process. The confirmWithdraw note adds a further gate ("Never set it on your own"), covering the approval path as well as the happy path.

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