Skip to main content
Glama
Sign In

URLinks

by me.urlinks
OverviewDiscussionsAdmin

create_shortlink

Create a new shortlink. The shortlink path must start with 'my/' (personal) or 'yt/' (YouTube globals). Once created, my/ shortlinks resolve publicly at https://urlinks.me/{alias}/{name} (assuming the user has set an alias via create_alias) — that's the URL QR codes encode for click tracking. Group shortlinks (e.g. work/foo) aren't supported through the API yet; use the web dashboard for those.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shortlink": "<shortlink>",
      "url": "<url>"
    },
    "name": "create_shortlink"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe destination URL the shortlink should redirect to
shortlinkYesThe short path. Must start with 'my/' (personal) or 'yt/' (YouTube). Examples: 'my/docs', 'my/standup', 'yt/never-gonna-give'.
descriptionNoOptional human-readable description of what this link is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive write. The description adds real behavior: the created link resolves publicly at a templated URL tied to the user's alias, which is what QR codes encode, and that alias setup is a separate precondition. It omits what happens on a duplicate/invalid shortlink (error vs. overwrite), which is the main remaining behavioral gap for a create operation.

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?

Front-loaded with the action and the naming constraint, then consequences, then the unsupported case. Three sentences, each doing work; the URL template detail is useful rather than padding, though it could be tightened.

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?

For a 3-parameter create tool with no output schema, the definition covers allowed paths, the alias prerequisite for the public URL, and the unsupported group-link path. An agent has everything needed to construct a valid call and set expectations for what the link will do.

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%, so all three parameters are already documented, including the 'my/' vs 'yt/' prefix rule and examples. The description largely restates that rule and adds only indirect context (alias-dependent resolution) rather than new per-parameter meaning, so the baseline of 3 applies.

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 opens with a specific verb+resource ('Create a new shortlink') and immediately constrains the allowed namespace ('my/' or 'yt/'). It does not explicitly contrast with likely siblings such as bulk_create_links or edit_link, so an agent must infer that this creates exactly one link.

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?

It names a clear when-not case ('Group shortlinks ... aren't supported through the API yet; use the web dashboard') and names a prerequisite tool (create_alias) for public resolution. It gives no guidance on single vs. bulk creation or on updating an existing link instead.

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

All URLinks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources