MiniURL

MiniURL tag_link

tag_link

Add a tag to a short link for campaign or category organisation.

Input Schema

TableJSON Schema

Name	Required	Description
`alias`	Yes	The link alias to tag.
`domain`	No	The link domain. Defaults to miniurl.com.
`tag_id`	Yes	The tag ID to assign.

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

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

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

Changed5 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"
```
- addedInput schema / properties / tag_id / minimum
```
Added value: +1
```
- changedInput schema / properties / tag_id / type
```
Previous value: -"number"New value: +"integer"
```
First observedJul 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already indicate the tool is not read-only (readOnlyHint false) and not destructive (destructiveHint false). The description adds no extra behavioral context such as whether tags are replaced, whether authentication is required, or rate limits. It is consistent with annotations but provides minimal additional value beyond stating the mutation action.

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 no redundant words. It efficiently states the action and purpose, earning every word it uses.

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?

The tool is a simple mutation with a fully described schema and an output schema present. However, the description omits any prerequisites (e.g., the tag must exist via create_tag) or special behavior (e.g., idempotency). While parameters are covered by the schema, the description lacks broader contextual guidance for when this action is valid.

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%, meaning all three parameters (alias, domain, tag_id) are fully described in the input schema. The description itself does not add any meaning beyond the schema, so the baseline of 3 is appropriate. The schema already documents the required fields and their purposes.

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 specifies the action 'Add' with the resources 'tag' and 'short link', and includes a purpose ('for campaign or category organisation'). This distinguishes it from sibling tools like create_tag (which creates a tag) and untag_link (which removes a tag).

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 explicit guidance on when to use this tool versus alternatives. It does not mention untag_link for removing tags, create_tag for creating tags, or any exclusions or prerequisites. The only implied usage is the organizational purpose, but without direct comparison or situational context.

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?