Skip to main content
Glama

AceRound AI Interview Copilot

delete_job_apply_profile_field

Destructive

Delete the value of one standard field in the user's Auto Apply profile (keys from get_job_apply_profile). Replies with the result as read back. 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": {
      "key": "<key>"
    },
    "name": "delete_job_apply_profile_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so irreversibility is partly covered; the description reinforces it and adds the required OAuth scope job_applications:write and a rough return statement ("result as read back"). That extra context is real but thin, and no error/empty-field behavior is described.

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: what it does, what it returns, then the safety obligation, front-loaded with the action. No redundant phrasing and nothing restates the schema.

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 definition covers scope, key source, irreversibility, confirmation, auth scope and response behavior. It stops short of stating behavior for unset fields or what the read-back actually contains.

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?

Schema description coverage is 0%, but the single parameter is a fully enumerated key list that documents itself. The description adds value by telling the agent where valid keys originate (get_job_apply_profile) and that only one field is affected per call.

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 one standard field's value in the Auto Apply profile, and pins the key source to get_job_apply_profile. The word "standard" implicitly separates it from delete_learned_profile_answer, though no sibling is named for contrast.

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 concrete precondition: tell the user what will be deleted and obtain their agreement before calling. It does not compare against update_job_apply_profile (e.g. whether setting an empty value is an alternative), so the alternative-routing piece is missing.

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