Gajo URL Shortener

Get a short link

get_url

Read-only

Look up one of your short links by code: destination, click count, status, and expiry. Use get_url_stats for clicks per day and where they came from.

Input Schema

Name	Required	Description	Default
`code`	Yes	The link's short code (e.g. AbCdEf, or launch for gajo.io/c/launch). A full short URL also works.

Output Schema

Name	Required	Description
`active`	No
`appLink`	No	App links only: where iOS and Android go, and the page other devices see.
`shortUrl`	Yes	Ready-to-share short link.
`shortCode`	Yes
`clickCount`	No
`createdDate`	No	ISO-8601 instant.
`expiresDate`	No	ISO-8601 instant; null when the link never expires.
`fallbackUrl`	No
`originalUrl`	Yes
`isCustomCode`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedOutput schema / properties / appLink

Added value: +{
+  "description": "App links only: where iOS and Android go, and the page other devices see.",
+  "properties": {
+    "androidUrl": {
+      "type": "string"
+    },
+    "appName": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "iconUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "iosUrl": {
+      "type": "string"
+    },
+    "otherwise": {
+      "enum": [
+        "mobile_only",
+        "store_links",
+        "store_badges"
+      ],
+      "type": "string"
+    },
+    "qrCodeUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "iosUrl",
+    "androidUrl",
+    "otherwise"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "active": {
+      "type": "boolean"
+    },
+    "clickCount": {
+      "type": "integer"
+    },
+    "createdDate": {
+      "description": "ISO-8601 instant.",
+      "type": "string"
+    },
+    "expiresDate": {
+      "description": "ISO-8601 instant; null when the link never expires.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fallbackUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "isCustomCode": {
+      "type": "boolean"
+    },
+    "originalUrl": {
+      "type": "string"
+    },
+    "shortCode": {
+      "type": "string"
+    },
+    "shortUrl": {
+      "description": "Ready-to-share short link.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "shortUrl",
+    "shortCode",
+    "originalUrl"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the lookup is scoped to 'your' short links and names the returned fields, but with an output schema present these details are already structured elsewhere, so added behavioral value is modest. No mention of behavior for an unknown code.

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?

Two short sentences, zero filler, with the core action front-loaded and the disambiguation appended. Every clause 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 one-parameter read tool with annotations, a full schema, and an output schema, the description is nearly sufficient. The only gap is unstated behavior for an invalid or nonexistent code, which the agent may want to know before calling.

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?

Single 'code' parameter with 100% schema description coverage, so the schema already explains the format (short code or full short URL). The description only says 'by code', adding nothing beyond the schema, which is the expected baseline here.

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?

States a specific verb ('look up') and resource ('one of your short links by code') and enumerates the fields returned (destination, click count, status, expiry). This makes it clearly distinguishable from get_url_stats and list_urls without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use get_url_stats for clicks per day and where they came from,' naming the alternative and the exact condition that selects it. Nothing about tool choice between these two is left to inference.

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

All Gajo URL Shortener tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?