Gajo URL Shortener

Create an app store link

create_app_link

Pro only: create one short link for a mobile app. iPhones and iPads that open it go to the app's App Store page, Android devices to its Google Play page, and any other device (such as a desktop) sees a Gajo page with a QR code to scan with a phone. Use it for a link that should send people to the right app store; for an ordinary link use shorten_url.

Input Schema

Name	Required	Description
`iosUrl`	Yes	Where iPhones and iPads go: the app's App Store page (https://apps.apple.com/.../id...) or, for a beta, its TestFlight link (https://testflight.apple.com/join/...).
`appName`	No	The app's name for the page. Optional: looked up from the App Store when omitted.
`otherwise`	Yes	The page every other device (such as a desktop) sees, always with a QR code of the link to scan with a phone: mobile_only says the link must be opened in a mobile browser; store_links lists both store URLs; store_badges shows the official App Store and Google Play badges under "Click below to download {appName}" and is only for apps published in both stores (use store_links or mobile_only for TestFlight and Google Play test links).
`androidUrl`	Yes	Where Android devices go: the app's Google Play page (https://play.google.com/store/apps/details?id=...) or a Google Play test link (https://play.google.com/apps/internaltest/... or /apps/testing/...).
`customCode`	No	Optional custom code (3-50 letters, digits, or hyphens) for a gajo.io/c/{code} link.

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.

Changed3 schema fields changedOct 24, 2026

changedInput schema / properties / androidUrl / description

Previous value: -"The app's Google Play URL (https://play.google.com/store/apps/details?id=...). Android devices go here."New value: +"Where Android devices go: the app's Google Play page (https://play.google.com/store/apps/details?id=...) or a Google Play test link (https://play.google.com/apps/internaltest/... or /apps/testing/...)."

changedInput schema / properties / iosUrl / description

Previous value: -"The app's App Store URL (https://apps.apple.com/...). iPhones and iPads go here."New value: +"Where iPhones and iPads go: the app's App Store page (https://apps.apple.com/.../id...) or, for a beta, its TestFlight link (https://testflight.apple.com/join/...)."

changedInput schema / properties / otherwise / description

Previous value: -"The page every other device (such as a desktop) sees, always with a QR code of the link to scan with a phone: mobile_only says the link must be opened in a mobile browser; store_links lists both store URLs; store_badges shows the official App Store and Google Play badges under \"Click below to download {appName}\"."New value: +"The page every other device (such as a desktop) sees, always with a QR code of the link to scan with a phone: mobile_only says the link must be opened in a mobile browser; store_links lists both store URLs; store_badges shows the official App Store and Google Play badges under \"Click below to download {appName}\" and is only for apps published in both stores (use store_links or mobile_only for TestFlight and Google Play test links)."

AddedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (non-readonly, non-destructive, non-idempotent, closed world), and the description adds real context on top: plan gating and per-device destination behavior including what a desktop visitor sees. It stops short of stating what happens on a customCode collision or whether the link is immediately live, which are the remaining behavioral unknowns for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the Pro gating and the core action, then the routing model, then the sibling routing. Slight overlap with the schema's own device descriptions, but nothing is wasted or buried.

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?

An output schema exists so return values need no explanation, the schema is fully documented, and annotations carry the safety profile. The description is complete enough to call correctly; only edge-case behavior (code collisions, whether the appName lookup can fail) is unaddressed.

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 coverage is 100% and the field descriptions already define iosUrl, androidUrl, and the three otherwise modes in detail. The description reinforces the device→destination model but adds no syntax, format, or constraint detail beyond what the schema states, so this sits at the baseline for a fully documented schema.

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 uses a specific verb and resource — "create one short link for a mobile app" — and immediately spells out the routing behavior (iOS → App Store, Android → Google Play, desktop → QR page). It explicitly separates itself from shorten_url, so an agent can pick between them 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?

It states the selecting condition directly: "Use it for a link that should send people to the right app store; for an ordinary link use shorten_url." It also names a prerequisite ("Pro only"), which is exactly the kind of gating an agent needs before calling.

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?