Skip to main content
Glama

Delete an achievement

delete_achievement
Destructive

Delete an achievement from your game, removing every player's unlock and removing it from all trophy cases. Prefer update_achievement to correct wording instead.

Instructions

Removes one achievement from a game you own. Read this part twice: every unlock of that badge is deleted with it, so it vanishes from the trophy case of every player who earned it, and the count does not come back if you re-declare the slug later. That cascade is on purpose — a badge whose meaning was removed should not linger on somebody's profile pointing at nothing — but it makes this the one call in the set worth pausing on. If the badge is right and its wording is wrong, use update_achievement. If your build still unlocks this slug, remove that call too, or players will hit a NOT_FOUND every run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameYesThe game, by slug (e.g. "orbital-drift") or by id (uuid).
slugYesThe stable key your game code passes to Arcade.achievements.unlock(). Lowercase letters, digits and hyphens, up to 48 characters — e.g. "first-win", "no-damage-run". Pick it once and keep it: renaming the name or description never breaks a shipped build, changing the slug breaks every call site in it.
Behavior5/5

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

Goes well beyond the destructiveHint annotation by disclosing that every unlock is deleted from every player's trophy case, the count won't return even if the slug is re-declared later, and that this cascade is intentional.

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?

The description is longer than average, but the length is justified by the irreversible destructive behavior. The core action is front-loaded and the warnings and alternatives are relevant. The 'Read this part twice' instruction is slightly extra but acceptable.

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?

Covers the operation, the irreversible cascade, the reason behind it, the correct alternative, and the follow-up action needed in client code. With rich annotations and full schema coverage, nothing necessary for correct selection or invocation is missing.

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 both parameters are already documented with examples and constraints. The description adds context about slug reuse but does not need to repeat parameter details.

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 and resource: 'Removes one achievement from a game you own.' It also distinguishes itself from update_achievement by clarifying that deletion is for removing a badge, not fixing wording.

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

Usage Guidelines5/5

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

Explicitly says when to use this tool vs update_achievement, warns that this is the destructive call in the set, and advises removing unlock calls in code to avoid NOT_FOUND errors. This is model guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elliothimmelfarb/aimade-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server