Skip to main content
Glama

Delete (un-deploy) an endpoint

delete_endpoint
Destructive

Permanently removes a deployed endpoint so its URL stops resolving and its configuration is deleted. Preview first without confirm; use withArchived to clear every version of the path.

Instructions

Permanently un-deploys an endpoint — its URL stops resolving and its configuration is removed (unlike toggle_endpoint, this cannot be undone by re-enabling it; deploy_endpoint would be needed to publish it again). Requires confirm=true — first call WITHOUT confirm to preview, then again with confirm:true. A MAIN endpoint whose path still has other versions (the archived, disabled copies each commit leaves — list_endpoints includeArchived shows them) is refused unless withArchived:true, which removes the whole path on that domain in one call (domain owner only). That is how a site moves to another domain: delete withArchived, redeploy.

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": {
      "endpointId": "<endpointId>"
    },
    "name": "delete_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to delete. Omit/false returns a preview only.
endpointIdYesThe endpoint's id — from list_endpoints.
withArchivedNoAlso delete every other version of this path on its domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description adds the consequences that matter — the URL stops resolving, configuration is removed, and the action is irreversible in a way toggle_endpoint is not. It further discloses a server-side refusal path (a MAIN endpoint with other versions is rejected unless withArchived:true) and a permission gate (domain owner only), which annotations could never convey.

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?

Front-loaded with the destructive outcome, then the confirm protocol, then the edge case — a sensible ordering with no filler sentences. The nested parenthetical explaining archived versions is dense and slightly hard to parse on first read, but it carries real information rather than padding.

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?

For a destructive, irreversible mutation with three parameters and no output schema, the description covers consequences, prerequisites, the preview workflow, the refusal condition, permission scope, and the migration use case. There is no gap an agent would need to guess at before invoking it correctly.

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%, so baseline is 3, and the description genuinely earns above it: withArchived is explained as removing the whole path on that domain in one call and restricted to the domain owner, and the confirm parameter is framed as a preview-then-confirm sequence rather than a bare boolean. endpointId's origin is already in the schema, so it adds nothing there, keeping it short of a 5.

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 — "Permanently un-deploys an endpoint" — and immediately scopes it against siblings: unlike toggle_endpoint it cannot be undone, and deploy_endpoint would be needed to publish again. An agent can distinguish delete from toggle/deploy without opening any schema.

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?

Gives an explicit two-step protocol (call without confirm to preview, then with confirm:true), names the alternatives and when each applies (toggle_endpoint for reversible disable, deploy_endpoint to republish, list_endpoints includeArchived to see versions), and states the withArchived condition plus the domain-owner restriction. Exclusions and prerequisites are both spelled out.

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