Goodeye

delete_skill_version

Destructive

Permanently and immediately erase a single non-current skill version.

This is permanent: the version row, all its attached files, and any content that is no longer referenced by any surviving version or published template version are removed from the live system at once. There is no recovery path. Use archive_skill if you want a reversible alternative for the whole skill.

Encrypted backups age out within the platform's standard retention window (up to three months), so the data is not instantly erased from all systems everywhere, but it is no longer accessible through any product surface after this call.

The current (live) version cannot be erased with this call. Use delete_skill to permanently remove the entire skill including its current version.

Version numbers remain monotonic with a gap where the erased version was. Surviving versions are not renumbered.

Owner only. Pointing at another user's skill raises NotFound.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version`	Yes	The non-current version number to permanently erase.
`skill_id`	Yes	The skill to act on, identified by its UUID, slug, or name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Description adds extensive behavioral context beyond annotations: permanence, no recovery, erasure of version row and attached files, backup retention window, version numbering gaps, and restriction against erasing current version. No contradiction with destructiveHint: true annotation.

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?

Description is well-structured: starts with the core action, then lists consequences, alternatives, and constraints. Each sentence is informative and necessary, with no fluff.

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?

Given the presence of an output schema and full input schema with annotations, the description covers all essential aspects: action, side effects, prerequisites, and alternatives. It is complete and self-contained.

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 coverage is 100% with descriptions, but the tool description adds extra meaning: clarifies that version must be 'non-current' and that skill_id can be UUID, slug, or name. This provides useful context beyond the schema.

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?

The description clearly states the verb ('erase') and resource ('single non-current skill version'), and distinguishes from sibling tools like archive_skill and delete_skill by specifying what each alternative does.

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 tells when to use this tool (for permanent erasure of a non-current version) and when not to (use archive_skill for reversible action, delete_skill for entire skill including current version). Also mentions owner-only access.

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

All Goodeye tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.