Skip to main content
Glama

面灵AI 面试助手

delete_interview

Destructive

删除一场面试记录,连同其报告与问答记录一并从列表中移除。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 interviews: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": {
      "interviewId": "<interviewId>"
    },
    "name": "delete_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
interviewIdYes面试 ID,取自 list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond that: it discloses the cascade (report and Q&A records also removed), irreversibility, a mandatory consent step, and the required authorization scope interviews:write. That is exactly the operational context an agent needs before invoking an irreversible mutation.

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-loaded with the action and its reach, then irreversibility, then the consent requirement and auth scope — a sensible escalation order. Slightly redundant in the 删除…从列表中移除 phrasing, but every clause contributes a distinct fact.

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, no-output-schema destructive tool, the description covers everything an agent needs: what is destroyed (including dependents), that it cannot be undone, the consent gate, and the auth scope. No meaningful gap remains.

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 coverage is 100% and interviewId already documents its format and that it comes from list_interviews, so the description adds no parameter-level detail. Baseline 3 applies when the schema carries the parameter semantics.

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?

States a specific verb+resource (删除一场面试记录) and adds scope detail that the name alone does not convey: the report and Q&A records are removed together, and the entry disappears from the list. It does not explicitly contrast itself with any sibling, but the cascade disclosure makes the operation unambiguous.

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 a procedural precondition — explain what will be deleted and obtain user consent before executing — which effectively tells the agent when this is appropriate to fire. It stops short of naming alternatives or stating when-not to use it (e.g., when the user merely wants to hide/rename a record, which siblings like rename_interview cover).

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