Gajo URL Shortener

Change an app store link

update_app_link

DestructiveIdempotent

Pro only: change an app link's App Store or Google Play URL, its app name, or the page other devices see. Only the fields you pass change. For an ordinary link's destination use update_url.

Input Schema

Name	Required	Description
`code`	Yes	The link's short code (e.g. AbCdEf, or launch for gajo.io/c/launch). A full short URL also works.
`iosUrl`	No	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`	No	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`	No	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/...).

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

Behavior4/5

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

The annotations already declare mutation, idempotency, and destructive behavior, so the description does not need to repeat them. It adds useful context that only passed fields change and that the tool is Pro-only, though it does not itself explain the destructive impact covered by annotations.

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 short and front-loaded, with the Pro constraint and mutation scope stated first. Every sentence contributes either scope, partial-update behavior, or sibling routing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations, complete schema coverage, and an output schema, the description supplies the remaining call-critical context: Pro-only availability, partial-update behavior, and when to use update_url instead.

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%, and the schema already explains code, iosUrl, androidUrl, appName, and the otherwise enum in detail. The description only paraphrases the field categories, adding little beyond the structured parameter documentation.

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 states a specific verb and resource: change an app link's App Store or Google Play URL, app name, or fallback page. It also explicitly distinguishes this from update_url, which handles ordinary link destinations.

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 gives a clear prerequisite ("Pro only") and names the alternative tool for ordinary link destinations. An agent can decide between update_app_link and update_url without opening either schema.

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?