Gajo URL Shortener

Get click stats

get_url_stats

Read-only

Get click analytics for one of your links, bots excluded: total clicks and clicks per day (7 days on Free, 90 on Basic, every day since the link was created on Pro). Basic and Pro also get referrers, devices, countries, and regions.

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
`shortCode`	Yes
`topRegions`	No
`clicksByDay`	Yes
`historyDays`	Yes	Days of history in clicksByDay.
`totalClicks`	Yes
`topCountries`	No
`topReferrers`	No
`deviceBreakdown`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "clicksByDay": {
+      "items": {
+        "properties": {
+          "clicks": {
+            "type": "integer"
+          },
+          "date": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "date",
+          "clicks"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "deviceBreakdown": {
+      "items": {
+        "properties": {
+          "device": {
+            "type": "string"
+          },
+          "percentage": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "device",
+          "percentage"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "historyDays": {
+      "description": "Days of history in clicksByDay.",
+      "type": "integer"
+    },
+    "shortCode": {
+      "type": "string"
+    },
+    "topCountries": {
+      "items": {
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "country": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "country",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topReferrers": {
+      "items": {
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "source": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "source",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topRegions": {
+      "items": {
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "region": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "region",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalClicks": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "shortCode",
+    "totalClicks",
+    "historyDays",
+    "clicksByDay"
+  ],
+  "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 readOnlyHint=true and openWorldHint=false, but the description adds real behavioral context beyond them: bots are excluded from the counts, retention is 7/90/unbounded days by plan, and richer dimensions (referrers, devices, countries, regions) are gated to Basic/Pro. It does not cover error cases or rate limits, but the disclosure load is well carried.

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?

A single dense sentence, front-loaded with the core purpose and the bots-excluded qualifier, followed by the tier breakdown. The stacked clauses and parentheticals make it slightly unwieldy, but no sentence is filler.

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?

An output schema exists, so return values need no explanation, and the description still previews the metric dimensions and their plan gating. For a single-parameter read tool this covers everything an agent needs to invoke it correctly.

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?

With 100% schema description coverage on a single 'code' parameter, the schema already does the heavy lifting, so baseline 3 applies. The description's 'for one of your links' reinforces that it takes exactly one link but adds no format or syntax detail beyond the schema's example values.

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 and resource ('Get click analytics for one of your links') and immediately scopes the result set ('bots excluded: total clicks and clicks per day'). The per-link framing distinguishes it from siblings like get_usage (account-level) and get_url (metadata), so an agent can route without opening the schema.

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?

Usage is implied by the analytics framing and the plan-tier table, but there is no explicit when-to-use-versus-alternatives statement and no named sibling (e.g., get_url for metadata, get_usage for quota). The tier gating tells the agent what it will get, not when it should choose this tool over another.

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?