Skip to main content
Glama

AceRound AI Interview Copilot

delete_learned_profile_answer

Destructive

Delete a learned answer so it is no longer filled into other applications. 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": {
      "normalized": "<normalized>"
    },
    "name": "delete_learned_profile_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
normalizedYesNormalized key of the learned answer, copied from get_job_apply_profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, but the description adds genuinely new information: the deletion is irreversible and a user confirmation step is mandated. It also discloses the required auth scope (job_applications:write), which annotations do not convey. Only the response behavior on missing keys is unstated.

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?

Three short sentences, front-loaded with the action and effect, then consequences, then auth. No filler; the parenthetical scope note is compressed rather than redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 effect, irreversibility, required confirmation, and auth scope — enough for correct invocation. Minor gaps like what happens for a nonexistent key are acceptable at this complexity.

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 description coverage is 100% and the single parameter documents that the normalized key is copied from get_job_apply_profile. The description adds no further meaning about the parameter, so baseline 3 applies.

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 and resource ('Delete a learned answer') and adds the observable effect ('no longer filled into other applications'), which distinguishes it from sibling edit_learned_profile_answer by effect rather than name. The sibling alternative is not referenced, so it stops short of full differentiation.

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 a clear precondition and interaction protocol: confirm with the user what will be deleted and obtain agreement before calling, plus the required scope. It does not mention edit_learned_profile_answer as the non-destructive alternative when the user only wants to change an answer, leaving that inference to the agent.

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