Skip to main content
Glama

面灵AI 面试助手

remove_job_application

Destructive

从投递清单中删除一条尚未投递的记录(AI 推荐、清单中未投、确认未提交的失败)。投递过的不能删除,改用 abandon_job_application。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 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
applicationIdYes投递记录 ID,从 list_job_applications 或加入清单的工具回包取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to establish that this is a write. It still adds real context beyond them: irreversibility ('删除后不能恢复'), the required user-consent step, and the authorization scope (job_applications:write). It stops short of describing the response or what happens if the ID is already gone, which keeps it from a 5.

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?

Content is front-loaded: the deletion scope comes first, the alternative second, the risk and consent requirement last. Every clause earns its place, though the heavy parenthetical nesting makes it denser than it needs to be.

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 mutation with no output schema, the definition covers everything needed to act safely: which records qualify, what to do instead for others, irreversibility, consent prerequisite, and auth scope.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that applicationId comes from list_job_applications or the add-to-list tools. The description text adds no further meaning about the parameter, so the baseline of 3 applies.

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 states a specific verb and resource ('从投递清单中删除一条尚未投递的记录') and narrows the scope to unsubmitted records, explicitly naming the sibling it is not ('投递过的不能删除,改用 abandon_job_application'). An agent can distinguish this from abandon_job_application without opening either 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?

It gives an explicit negative condition (submitted records cannot be deleted here) together with the alternative to use instead, plus a required pre-step (explain what will be deleted and obtain user consent). Both when-to-use and when-not-to-use are covered.

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