Skip to main content
Glama

面灵AI 面试助手

delete_job_apply_profile_field

Destructive

删除用户网申档案中一个标准字段的值(键名见 get_job_apply_profile)。回包为读回的结果。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 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": {
      "key": "<key>"
    },
    "name": "delete_job_apply_profile_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes well beyond them: it states the deletion is irreversible, requires the job_applications:write authorization scope, mandates user consent before execution, and specifies that the response is the read-back profile result. These are exactly the operational facts an agent needs for a destructive mutation that annotations alone cannot convey.

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?

It is a single dense sentence with the action front-loaded, followed by return behavior, the irreversibility/consent warning, and the auth scope. Every clause carries information; the stacked parentheticals make it slightly harder to scan than ideal but nothing is wasted.

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 description covers everything material: what is removed, where valid keys come from, what the response contains, that the action cannot be undone, that consent must be obtained first, and which authorization scope is required. Nothing an agent needs in order 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required 'key' parameter with 0% schema description coverage, but the schema itself enumerates 74 valid values, and the description adds the meaning that these are 'standard fields' whose key names are documented in get_job_apply_profile. That extra pointer helps the agent locate and interpret the enum rather than leaving it as a bare value list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and object — deleting the value of one standard field in the user's job-application profile — and points to get_job_apply_profile as the source of valid key names. It is clearly distinct from an update-style operation, though it never names update_job_apply_profile as the sibling used to set a value, so the contrast is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives procedural conditions (explain to the user what will be deleted and obtain consent before executing) and routes the agent to get_job_apply_profile for key enumeration. However, it never says when to prefer this over update_job_apply_profile (e.g., clearing a field by setting an empty value) or any case where deletion should not be used, so the routing to the alternative is left implicit.

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