Skip to main content
Glama

L1NK

by website.l1nk
OverviewDiscussionsAdmin

Create short link

create_link

Create a short link that redirects to a URL. Returns shortUrl, which is what you share.

Input Schema

NameRequiredDescriptionDefault
urlYesDestination URL. https:// is added if missing.
nameNoOptional label to recognise the link in the dashboard.
tagsNoOptional tags to group links, e.g. ["table-1","instagram"] (max 10, up to 30 characters each; letters, numbers, - and _; stored lowercase). Adding tags is Pro (also during the 14-day trial).
aliasNoOptional custom alias (letters, numbers, - and _; max 20 characters, never truncated: a longer one is rejected). Pro plan only (also during the 14-day trial): on Free, omit it and the link gets a random code.
domainNoOptional domain the user owns and has connected to L1NK (Pro plan only), to put the link on, e.g. go.mybrand.com. It must be active.
domain_idNoOptional id of a verified custom domain (use domain instead).
time_zoneNoOptional IANA time zone (e.g. America/Lima) used to write the activation date to visitors. Default UTC.
max_clicksNoOptional. Pro plan. The link stops working after this many people (bots are not counted). Approximate at the boundary under simultaneous clicks.
active_fromNoOptional. Pro plan. ISO 8601 date-time (e.g. 2026-11-03T09:00:00-05:00): before it the link does not redirect and shows "this link becomes active on …".
expires_in_daysNoOptional expiry. Pro plan only.
unavailable_pageNoOptional. Pro plan. What visitors see when the link is expired, past max_clicks or not active yet. {"modo":"neutra"} = the neutral L1NK page (default); {"modo":"url","url":"https://..."} = redirect to that fallback URL; {"modo":"mensaje","mensaje":"..."} = a short message of yours (max 200 characters). Shown on the same host, custom domains included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / alias / description
      Previous value: -"Optional custom alias (letters, numbers, - and _; max 20). Pro plan only (also during the 14-day trial): on Free, omit it and the link gets a random code."New value: +"Optional custom alias (letters, numbers, - and _; max 20 characters, never truncated: a longer one is rejected). Pro plan only (also during the 14-day trial): on Free, omit it and the link gets a random code."
    • addedInput schema / properties / alias / maxLength
      Added value: +20
  2. Changed6 schema fields changed
    • addedInput schema / properties / active_from
      Added value: +{
+  "description": "Optional. Pro plan. ISO 8601 date-time (e.g. 2026-11-03T09:00:00-05:00): before it the link does not redirect and shows \"this link becomes active on …\".",
+  "maxLength": 40,
+  "type": "string"
+}
    • changedInput schema / properties / alias / description
      Previous value: -"Optional custom alias (letters, numbers, - and _; max 20)."New value: +"Optional custom alias (letters, numbers, - and _; max 20). Pro plan only (also during the 14-day trial): on Free, omit it and the link gets a random code."
    • addedInput schema / properties / max_clicks
      Added value: +{
+  "description": "Optional. Pro plan. The link stops working after this many people (bots are not counted). Approximate at the boundary under simultaneous clicks.",
+  "maximum": 1000000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Optional tags to group links, e.g. [\"table-1\",\"instagram\"] (max 10, up to 30 characters each; letters, numbers, - and _; stored lowercase). Adding tags is Pro (also during the 14-day trial).",
+  "items": {
+    "maxLength": 30,
+    "pattern": "^[^,]{1,30}$",
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
    • addedInput schema / properties / time_zone
      Added value: +{
+  "description": "Optional IANA time zone (e.g. America/Lima) used to write the activation date to visitors. Default UTC.",
+  "maxLength": 64,
+  "type": "string"
+}
    • addedInput schema / properties / unavailable_page
      Added value: +{
+  "description": "Optional. Pro plan. What visitors see when the link is expired, past max_clicks or not active yet. {\"modo\":\"neutra\"} = the neutral L1NK page (default); {\"modo\":\"url\",\"url\":\"https://...\"} = redirect to that fallback URL; {\"modo\":\"mensaje\",\"mensaje\":\"...\"} = a short message of yours (max 200 characters). Shown on the same host, custom domains included.",
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Optional custom domain of the account to put the link on, e.g. go.mybrand.com. It must be active."New value: +"Optional domain the user owns and has connected to L1NK (Pro plan only), to put the link on, e.g. go.mybrand.com. It must be active."
  4. Changed2 schema fields changed
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Optional custom domain of the account to put the link on, e.g. go.mybrand.com. It must be active.",
+  "maxLength": 253,
+  "pattern": "^[a-zA-Z0-9.-]+$",
+  "type": "string"
+}
    • changedInput schema / properties / domain_id / description
      Previous value: -"Optional id of a verified custom domain of the account."New value: +"Optional id of a verified custom domain (use domain instead)."
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is structured. The description adds the return contract ('Returns shortUrl, which is what you share'), which is genuinely useful, but it never spells out the practical consequence of non-idempotency — that repeat calls mint additional links — nor plan gating at the top level.

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?

Two sentences, zero filler, and the most agent-relevant fact (you share shortUrl, not the input URL) is front-loaded rather than 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?

For an 11-parameter creation tool this is thin prose, but the schema is exceptionally detailed (100% coverage, nested object documented, plan limits inline) and annotations cover the mutation profile. The one meaningful omission is that duplicate invocations create separate links, which an agent should know before retrying.

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 all 11 parameters, including the nested unavailable_page object and the Pro-only constraints, are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 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 definition pairs the specific verb 'Create' with the concrete resource 'short link' and adds its effect ('redirects to a URL'), so it is unmistakable against siblings like get_link, update_link and delete_link. It does not explicitly name a sibling or contrast with one, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus update_link (for changing an existing link) or list_links/get_link (for finding one), and no prerequisites such as plan requirements are surfaced in the description. The only usage-shaped content is a hint about sharing shortUrl, which is about the result rather than the decision to call the tool.

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

All L1NK 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