MiniURL

MiniURL check_alias

check_alias

Read-onlyIdempotent

Check whether a custom alias is available on a given domain before creating a link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`alias`	Yes	The alias to check.
`domain`	No	The domain to check on. Defaults to miniurl.com.

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.

Changed1 schema field changedAug 8, 2026
- addedOutput schema / properties / data / properties / exists
```
Added value: +{
+  "type": "boolean"
+}
```

Changed8 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
```

addedOutput schema / properties / data / properties

Added value: +{
+  "alias": {
+    "type": "string"
+  },
+  "available": {
+    "type": "boolean"
+  }
+}

changedOutput schema / properties / data / type

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

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

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

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about the operation's purpose (availability check) but does not disclose additional behavioral traits like rate limits or error behavior. This is acceptable given the annotations, but it does not go beyond them.

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, focused sentence that delivers the purpose and usage context without any fluff. Every word contributes meaning, and it is front-loaded with the key action ('Check whether').

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 simple read-only check operation with rich annotations and an output schema present, the description sufficiently covers the core use case. It does not need to explain return values due to the output schema. Minor gap: no explicit alternatives list, but overall context is complete for the tool's simplicity.

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?

The input schema fully describes both parameters ('alias' and 'domain'), providing 100% coverage. The description's phrase 'on a given domain' aligns with the domain parameter but does not add new semantic meaning beyond what the schema already states. Baseline of 3 is appropriate.

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 tool's function with a specific verb ('check') and resource ('custom alias availability'), and frames it with a practical use case ('before creating a link'). It distinguishes itself from sibling tools like get_link or shorten_url, which focus on existing links or creation.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool ('before creating a link'), which effectively signals its intended role in the link-creation workflow. However, it does not explicitly name alternative tools or state when not to use it, so it lacks full exclusionary guidance.

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?