Skip to main content
Glama

Delete a tracked job application

deleteApplication
Destructive

Remove a job from the candidate's job tracker, with its notes and document links. It does not withdraw anything with the company. Confirm with the candidate 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": {
      "applicationId": "<applicationId>"
    },
    "name": "deleteApplication"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYesThe id from a listApplications result.

Output Schema

NameRequiredDescriptionDefault
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, so the bar is lower, yet the description still adds real value: it discloses the cascade (notes and document links are removed too), clarifies that the employer-side application is untouched, and adds a confirmation requirement plus a data-recording disclosure. No contradiction with the annotations.

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?

The functional content is front-loaded in two tight sentences with zero waste, and the cascade detail lands before the disclaimers. The trailing privacy/usage-tracking sentence is boilerplate noise but appears to be a mandated disclosure, and it is separated so it does not obscure the operational content.

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 single-parameter destructive mutation, the definition covers what is destroyed, what is not, and the human-confirmation prerequisite, while annotations carry the safety profile and an output schema exists so return values need not be described. Nothing an agent needs to call it safely is missing.

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 description coverage is 100% and the single applicationId parameter is fully documented in the schema ("The id from a listApplications result"). The description adds no extra meaning about the identifier, which is the expected baseline when the schema does the work.

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 uses a specific verb+resource pair ("Remove a job from the candidate's job tracker") and immediately scopes the effect to the tracker entry with its notes and document links. That scope distinguishes it from the many other delete* siblings (deleteResume, deleteCoverLetter) without needing to name them.

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 gives an explicit precondition ("Confirm with the candidate before calling") and a clear negative boundary ("It does not withdraw anything with the company"), which is exactly the misuse an agent would otherwise make. It stops short of naming an alternative for non-destructive cleanup (e.g. updateApplication), so it is clear context rather than full when/when-not/alternatives guidance.

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