Skip to main content
Glama

Delete my Clera account

deleteMyAccount
Destructive

Permanently delete the candidate's Clera account and everything Clera holds about them, the same as Delete account on the Account page. It cannot be undone, and this connection stops working right after.

Only when the candidate asks to delete their account. First ask why they want to leave and pass their answer in their own words as reasonText; reason is the closest of found_a_job, no_longer_job_searching, too_many_messages, privacy_concerns, not_the_right_opportunities, other. Never invent a reason. If they only want fewer messages or a break, offer setEmailSubscription or setJobSearchStatus first.

Two calls. Without code, Clera emails a 6-digit code to their login address; tell them where it went and ask them to read it to you. Then call again with the same reason and their code. The code works for 15 minutes; never guess one.

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": {
      "reason": "<reason>",
      "reasonText": "<reasonText>"
    },
    "name": "deleteMyAccount"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoThe 6-digit code from the email Clera sent the candidate. Leave out to send the code.
reasonYes
reasonTextYesWhy they are leaving, in the candidate's own words.

Output Schema

NameRequiredDescriptionDefault
stepYes
sentToYes
expiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, but the description adds consequences the annotations cannot: the deletion is irreversible, the connection stops working immediately afterward, and inputs/results are recorded for usage tracking. It also discloses the two-call verification flow and the 15-minute code window, though it does not say whether a failed or expired code requires restarting the flow.

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 destructive outcome and irreversibility in the first sentence, then sequences guidance, the two-call mechanics, and the privacy note. It is dense and multi-topic but every sentence carries operational information; the reason-category enumeration is the only mildly verbose stretch.

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, multi-step, consent-sensitive operation this covers the trigger condition, alternatives to try first, required inputs, the verification round trip, code lifetime, and the fact that results are logged. With an output schema present, the description needs no return-value detail, so nothing material 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?

Adds real meaning beyond the 67%-covered schema: reasonText must be the candidate's own words, reason must be the closest enum match, and code must be read back from the emailed 6-digit code with the same reason repeated on the second call. The one gap is that it never clarifies edge cases such as whether reasonText can be reused verbatim across both calls, but overall it compensates well for the partial schema coverage.

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 ("Permanently delete the candidate's Clera account and everything Clera holds about them") and pins scope precisely, distinguishing it from siblings like deleteApplication or deleteResume by making clear this is account-level erasure. The comparison to "Delete account on the Account page" gives a concrete anchor for what the action is.

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 trigger ("Only when the candidate asks to delete their account") plus explicit alternatives and the condition that selects them: offer setEmailSubscription or setJobSearchStatus first if the candidate only wants fewer messages or a break. It also instructs the agent to ask why and never invent a reason, which steers behavior rather than leaving it to inference.

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