Skip to main content
Glama

Delete a Hosted App version

delete_app_version
DestructiveIdempotent

Delete one non-current app version; the current version is refused with hosted_app_version_current.

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": {
      "version_id": "<version_id>"
    },
    "name": "delete_app_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoApp slug; provide exactly one of slug or app_id
app_idNoApp UUID; provide exactly one of slug or app_id
version_idYesStored version UUID belonging to this app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real value by disclosing the specific failure mode and error code for current versions, though it does not say whether the delete is reversible or what happens to related staged files.

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?

A single front-loaded sentence with the scope constraint and the failure condition packed in; no filler, no restatement of the title.

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 three-parameter destructive delete with full schema coverage and annotations, the description covers purpose, scope, and the main error case. It could go further on irreversibility and side effects on dependent resources, but nothing essential to correct 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%, so the schema already documents slug, app_id, and version_id including the one-of rule between slug and app_id. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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?

Names a specific verb and resource ('Delete one non-current app version') and constrains the target to non-current versions, which separates it from delete_app (whole app) and set_app_current_version. It stops short of naming any sibling as an explicit alternative, so it is clear but not maximally differentiating.

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

Usage Guidelines3/5

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

Gives a clear when-not rule: the current version is refused with 'hosted_app_version_current', which tells the agent the precondition for success. However, it never says what to do instead when that error occurs (e.g., set a different current version first), leaving recovery guidance implicit.

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