Skip to main content
Glama

AceRound AI Interview Copilot

remove_job_application

Destructive

Delete an application that was never submitted (suggested, on the list, or a failure confirmed before submitting). Submitted ones cannot be deleted; use abandon_job_application. Deletion cannot be undone; tell the user what will be deleted and get their agreement first. (Requires the user's sign-in with scope job_applications:write.)

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": "remove_job_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYesApplication id, from list_job_applications or the reply of an add-to-list tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversibility warning overlaps with structured data. What the description adds beyond it is real but modest: the exact eligibility rule and the job_applications:write auth scope. It does not say whether the record can later be recovered via restore_job_application.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each doing distinct work: eligibility, the alternative, the consent requirement plus auth scope. Nothing is repeated and the most important constraint (which applications qualify) is front-loaded.

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 one-parameter destructive tool with no output schema, it covers eligibility, the sibling alternative, irreversibility, required user consent, and auth scope. An agent has everything needed to call it correctly and safely.

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 single applicationId parameter is already documented with its provenance (from list_job_applications or an add-to-list reply). The description adds no parameter-specific meaning, but with one fully described required param the baseline of 3 is comfortably met.

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?

Specific verb plus resource ("Delete an application") with an explicit eligibility scope: never submitted, i.e. suggested, on the list, or a failure confirmed before submitting. It also names the sibling it is not (abandon_job_application), so an agent can route correctly 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?

Gives an explicit exclusion ("Submitted ones cannot be deleted") and names the alternative that handles that case. It also states the required precondition of confirming with the user before acting, which is a usage rule, not just a warning.

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