MiniURL

MiniURL update_link

update_link

Update a registered short link. Some fields require Pro.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	New HTTP or HTTPS destination URL. Requires Pro.
`alias`	Yes	The link alias to update.
`domain`	No	The link domain. Defaults to miniurl.com.
`dry_run`	No	Validate and preview the update without changing the link. Agent tokens only.
`password`	No	Set or replace the password. Requires Pro.
`expiration`	No	Set a new ISO 8601 expiration datetime. Requires Pro.
`activated_at`	No	Set a new ISO 8601 activation datetime. Requires Pro.
`clear_password`	No	Remove the current password.
`idempotency_key`	No
`clear_expiration`	No	Clear the current expiration.
`clear_activated_at`	No	Clear the current scheduled activation datetime.

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"
+]

Changed7 schema fields changedAug 7, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
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"
+]

Changed1 schema field changedAug 7, 2026

addedInput schema / properties / dry_run

Added value: +{
+  "description": "Validate and preview the update without changing the link. Agent tokens only.",
+  "type": "boolean"
+}

Changed2 schema fields changedAug 7, 2026

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"
+}

Changed7 schema fields changedJul 11, 2026
- addedInput schema / properties / activated_at / format
```
Added value: +"date-time"
```
- addedInput schema / properties / alias / maxLength
```
Added value: +64
```
- addedInput schema / properties / alias / minLength
```
Added value: +1
```
- addedInput schema / properties / domain / format
```
Added value: +"hostname"
```
- addedInput schema / properties / expiration / format
```
Added value: +"date-time"
```
- changedInput schema / properties / url / description
```
Previous value: -"New destination URL. Requires Pro."New value: +"New HTTP or HTTPS destination URL. Requires Pro."
```
- addedInput schema / properties / url / format
```
Added value: +"uri"
```
First observedJul 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the mutation nature is clear. The description adds the Pro requirement for some fields, which is useful scoping context. However, it does not disclose whether updates are partial or full replacement, or any side effects beyond annotation hints.

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 concise sentence that immediately conveys the tool's purpose and the most important caveat. No fluff or redundancy; every word contributes.

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 has 11 parameters and an output schema, the description is thin. It does not explain the update semantics (e.g., partial update), the dry_run validation option, or scenarios when to use this tool, relying almost entirely on schema and annotations. It is minimally sufficient but lacks the context an agent might need to safely invoke it.

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 coverage is high (91%), with most parameters having descriptive text. The description's 'Some fields require Pro' aligns with schema notes like 'Requires Pro' on url, password, and expiration fields, adding no new semantic info 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 'Update a registered short link', using a specific verb and resource. This differentiates it from sibling tools like shorten_url (create) and delete_link (delete), making the tool's purpose unambiguous.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. The only contextual hint is 'Some fields require Pro', which is a prerequisite/caveat rather than usage direction. No mention of when not to use it or which sibling to prefer.

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?