Skip to main content
Glama

AceRound AI Interview Copilot

delete_interview

Destructive

Delete an interview record, including its report and transcript. Deletion cannot be undone; tell the user what will be deleted and get their agreement first. (Requires the user's sign-in with scope 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
interviewIdYesInterview id from list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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, yet the description adds genuinely new behavioral facts: the deletion cascades to the report and transcript, it is irreversible, and it requires a specific OAuth scope. These are consequences and preconditions an agent cannot derive from the annotations or schema.

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 with zero waste: scope and cascade first, then the irreversibility/confirmation requirement, then the auth prerequisite. Front-loaded and each sentence earns its place.

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, everything an agent needs is present: what gets destroyed, that it is permanent, the consent workflow, 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 the single interviewId parameter is already documented as coming from list_interviews, so the description adds no parameter-level meaning. Baseline 3 applies when the schema carries the full burden.

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?

States a specific verb (delete) and resource (interview record), and goes further by naming the cascade scope — report and transcript — which distinguishes it from siblings like delete_exam, delete_resume, or delete_knowledge_base. An agent knows exactly what record class this removes.

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?

Gives explicit behavioral guidance for invocation: tell the user what will be deleted and get agreement before calling, plus the required auth scope (interviews:write). It does not name sibling alternatives or state when-not-to-use, but the confirmation prerequisite is a clear usage condition rather than an implied one.

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