Skip to main content
Glama

MiniURL

by io.github.addychang

MiniURL create_tag

create_tag

Create a new tag for organising links. Maximum 20 tags per account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTag name, 1-30 characters.
colorNoTag colour hex code. Defaults to #6b7280 (grey).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaNo
errorNo
successYes
approvalNo
retryableNo
request_idYes
retry_afterNo
next_actionsNo
required_scopeNo
user_action_requiredNo

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / properties / data / type
      Previous value: -[
-  "object",
-  "array",
-  "null"
-]New value: +[
+  "object",
+  "array",
+  "string",
+  "number",
+  "boolean",
+  "null"
+]
  2. Changed7 schema fields changed
    • 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"
+]
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed2 schema fields changed
    • addedInput schema / properties / name / maxLength
      Added value: +30
    • addedInput schema / properties / name / minLength
      Added value: +1
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations are all false (not read-only, not idempotent, etc.), but the description adds a valuable behavioral constraint: 'Maximum 20 tags per account.' This helps the agent anticipate a potential failure condition. However, it does not disclose behavior for duplicate tag names or error handling, leaving some transparency gaps.

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 extremely concise: two short sentences with no irrelevant information. It front-loads the core action and then adds a key constraint. Every word earns its place.

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 create operation with an output schema and annotations, the description provides the essential purpose and a critical account-level limit. It does not mention uniqueness restrictions or what happens when the limit is exceeded, but overall it is sufficient for an AI to invoke the tool appropriately.

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?

Input schema covers 100% of parameters with descriptions, so the description does not need to repeat parameter details. It adds no extra semantic meaning beyond the schema, which aligns with the baseline score of 3 for high schema coverage.

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 purpose: 'Create a new tag for organising links.' This is a specific verb+resource combination that distinguishes it from sibling tools like delete_tag and list_tags. The added constraint 'Maximum 20 tags per account' also provides meaningful context about the operation's scope.

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 a new tag is needed, but it does not explicitly discuss when to use this tool versus alternatives such as list_tags for checking existing tags or tag_link for associating tags. The 20-tag limit hints that users might need to check the current count first, but this is not directly stated.

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

All MiniURL toolsInspect
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