MiniURL

MiniURL delete_link

delete_link

Destructive

Delete a registered short link permanently.

Input Schema

TableJSON Schema

Name	Required	Description
`alias`	Yes	The alias to delete.
`domain`	No	The link domain. Defaults to miniurl.com.
`dry_run`	No	Preview the deletion and affected link scope without writing. Human approval is still required for the real delete.
`approval_id`	No	Approval id returned by a previous USER_APPROVAL_REQUIRED response.
`approval_token`	No	Legacy compatibility field; normally omit it and retry with approval_id after approval.
`idempotency_key`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`meta`	No
`error`	No
`success`	Yes
`approval`	No
`retryable`	No
`request_id`	Yes
`retry_after`	No
`next_actions`	No
`required_scope`	No
`user_action_required`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedAug 8, 2026

addedInput schema / properties / idempotency_key / pattern
```
Added value: +"^[A-Za-z0-9._:-]{8,128}$"
```

changedOutput schema / properties / data / type

Previous value: -[
-  "object",
-  "array",
-  "null"
-]New value: +[
+  "object",
+  "array",
+  "string",
+  "number",
+  "boolean",
+  "null"
+]

Changed9 schema fields changedAug 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / approval_token / description

Previous value: -"One-time approval token returned after a human approves the request."New value: +"Legacy compatibility field; normally omit it and retry with approval_id after approval."

addedInput schema / properties / dry_run

Added value: +{
+  "description": "Preview the deletion and affected link scope without writing. Human approval is still required for the real delete.",
+  "type": "boolean"
+}

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
addedOutput schema / properties / data / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / data / type

Previous value: -[
-  "object",
-  "array",
-  "string",
-  "number",
-  "boolean",
-  "null"
-]New value: +[
+  "object",
+  "array",
+  "null"
+]

changedOutput schema / properties / error / oneOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "required_scope": {
-        "type": "string"
-      },
-      "retry_after": {
-        "minimum": 0,
-        "type": "integer"
-      },
-      "retryable": {
-        "type": "boolean"
-      },
-      "user_action_required": {
-        "type": "boolean"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "required_scope": {
+        "type": "string"
+      },
+      "retry_after": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "retryable": {
+        "type": "boolean"
+      },
+      "user_action_required": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "message",
+      "retryable"
+    ],
+    "type": "object"
+  }
+]

addedOutput schema / properties / request_id / minLength
```
Added value: +8
```

changedOutput schema / required

Previous value: -[
-  "request_id"
-]New value: +[
+  "success",
+  "request_id"
+]

Changed4 schema fields changedAug 7, 2026

addedInput schema / properties / approval_id

Added value: +{
+  "description": "Approval id returned by a previous USER_APPROVAL_REQUIRED response.",
+  "type": "string"
+}

addedInput schema / properties / approval_token

Added value: +{
+  "description": "One-time approval token returned after a human approves the request.",
+  "type": "string"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "maxLength": 128,
+  "minLength": 8,
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "approval": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "data": {
+      "type": [
+        "object",
+        "array",
+        "string",
+        "number",
+        "boolean",
+        "null"
+      ]
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "required_scope": {
+              "type": "string"
+            },
+            "retry_after": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "user_action_required": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        }
+      ]
+    },
+    "meta": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "next_actions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "request_id": {
+      "type": "string"
+    },
+    "required_scope": {
+      "type": "string"
+    },
+    "retry_after": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "user_action_required": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "request_id"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJul 11, 2026
- addedInput schema / properties / alias / maxLength
```
Added value: +64
```
- addedInput schema / properties / alias / minLength
```
Added value: +1
```
- addedInput schema / properties / domain / format
```
Added value: +"hostname"
```
First observedJul 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, so the description adds the 'permanently' qualifier and 'registered' scope, which is useful extra context. However, it omits significant behavioral traits such as the human approval flow (suggested by approval_id/approval_token) and the dry_run preview capability, leaving those to be inferred from the schema.

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?

The description is a single, front-loaded sentence with zero waste: 'Delete a registered short link permanently.' It communicates the core function and key constraint (permanence) efficiently, earning top marks for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (dry_run, approval tokens, idempotency key) and the rich schema/output schema, the one-sentence description is somewhat thin. It doesn't hint at the multi-step approval workflow or the ability to preview deletions, but the schema and annotations together provide enough context for an agent to operate correctly. The description is adequate but not comprehensive.

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 83%, so the baseline is 3. The description itself does not add any parameter-level meaning, but the schema already documents most parameters in detail (e.g., dry_run, approval_id). The description provides no additional semantic value beyond what the schema fields already convey.

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 uses a specific verb ('Delete') and resource ('registered short link') with an explicit scope ('permanently'), making the tool's function unambiguous. It clearly distinguishes from sibling tools like delete_domain or delete_tag, which target different resources.

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?

The description implies usage ('when you want to permanently delete a short link') but provides no explicit guidance on when to prefer this tool over alternatives, no prerequisites, and no exclusion cases. It relies on the tool's name and obvious purpose rather than offering actionable selection criteria.

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

All MiniURL tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a clearly distinct resource and action: links, domains, tags, auth, and account status are all separate concerns. Even similar tools like shorten_url and bulk_create_links are differentiated by single vs. batch creation, and check_alias is distinct from get_link by checking availability before creation.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_domain, delete_link, list_tags, verify_registration_code). Mixed verb styles like tag/untag and shorten_url are still predictable and fit the established convention.

Tool Count3/5

At 23 tools, the set is on the heavy side and falls in the 16-25 borderline range. The number is somewhat justified by the broad scope (links, domains, tags, auth, analytics), but it approaches the upper limit where an agent may have difficulty selecting between many options.

Completeness5/5

The tool surface covers the full lifecycle of short links (create, read, update, delete, list, stats), domain management (add, delete, verify, list), tags (create, list, delete, tag/untag), and account/auth flows (guest tokens, registration, pro upgrade). It is hard to identify any critical missing operation for the stated purpose.

Resources

Need Help?