Gajo URL Shortener

Shorten a URL

shorten_url

Create a gajo.io short link for a URL and return it as shortUrl. Links follow your plan's code length and lifetime and count against its monthly quota. Pro plans can pass customCode for a branded gajo.io/c/{code} link, or shorten app deep links (myapp://...) with a web fallbackUrl.

Input Schema

Name	Required	Description
`url`	Yes	The long URL to shorten (http, https, mailto, tel, ftp, sftp; Pro: app deep links).
`customCode`	No	Pro only: custom code (3-50 letters, digits, or hyphens). Can't be combined with lifetimeDays.
`fallbackUrl`	No	Pro, deep links only: web URL used when the app isn't installed.
`lifetimeDays`	No	Days until the link expires; capped at your plan maximum.

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/5.0

Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent mutation. The description adds important behavioral context beyond annotations: quota consumption, plan-driven link lifetime, and the branded link format for customCode. It doesn't cover failure modes or rate limits, but the added quota and plan constraints are meaningful.

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?

Three compact sentences, with the primary action and return value front-loaded, followed by plan-level behavior and Pro-specific parameter nuances. No filler or repetition.

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?

Given full schema coverage, annotations, and an output schema, the description supplies the missing operational context: quota impact, plan-based lifetime, and Pro-only features. It is largely complete, though it could mention error conditions or whether the short URL is immediately active.

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%, so the schema already fully documents all four parameters. The description reinforces Pro-only usage for customCode and fallbackUrl and mentions the branded URL path, but adds little parameter-level detail beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Create a gajo.io short link for a URL') and states the return field ('shortUrl'). It distinguishes itself from read/delete/update siblings but only partially separates from create_app_link, since it also mentions deep links with fallbackUrl.

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 about plan-based behavior: links follow the plan's code length and lifetime, count against monthly quota, and Pro-only features are called out. It doesn't explicitly exclude or name alternatives like create_app_link, so it stops short of full when-to-use guidance.

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?