urlhub

Make a set of links

make_set

Idempotent

Makes a urlhub set from links: a short link that opens a page with every link's picture, title and description, and its QR code as PNG and SVG files. Good when several links should travel together: sent to someone, opened later on a phone, or printed as one QR code on a poster or a slide (gift ideas, products to compare, a reading list, a trip plan, links for a class). With a title (and a description) it publishes the set as a page with that heading, for a set to send round or print; without one it makes a short link. Both are public to anyone who has the link. The same links always give the same link; to change a set, call make_set again. A short link nobody opens for 90 days goes away, a page after a year; long_link, when the list is short enough, holds every link in the address itself and never goes away.

Input Schema

Name	Required	Description
`lang`	No	The page's language (en by default)
`urls`	Yes	The links, in the order to show them (1 to 200, http or https)
`view`	No	table (the default) or tiles with big pictures, for products and looks
`title`	No	A heading for the set, e.g. "Gift ideas for Dad under $50": makes a page
`description`	No	A line under the heading (only with a title)

Output Schema

Name	Required	Description
`kind`	Yes	page when a title was given
`link`	Yes	The link to give the person
`count`	Yes	How many links the set has
`qr_png`	Yes	The QR code of the link (PNG)
`qr_svg`	Yes	The same code as SVG, to print
`as_text`	Yes	The set as Markdown
`long_link`	No	The same links in one address (?urls=) that never goes away, without the title; only when they fit in an address
`expires_after_days_unopened`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / long_link

Added value: +{
+  "description": "The same links in one address (?urls=) that never goes away, without the title; only when they fit in an address",
+  "format": "uri",
+  "type": "string"
+}

First observedOct 6, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations (readOnly false, destructive false, idempotent true, openWorld true), the description discloses genuinely new traits: both outputs are public to anyone with the link, idempotency is reinforced ('the same links always give the same link; to change a set, call make_set again'), and expiry windows are spelled out (90 days for an unopened short link, a year for a page) plus the never-expiring long_link behavior. These are exactly the operational details an agent cannot infer from annotations.

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?

The definition is front-loaded: the core purpose leads, then usage contexts, then the behavioral caveats. It is dense and readable, but the parenthetical example lists (gift ideas, products to compare, a reading list, a trip plan, links for a class) run long and slightly dilute the signal without adding decision-relevant information.

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 a 5-parameter tool, full schema coverage, and an existing output schema, the description supplies everything else the agent needs: what is created, how title toggles page vs short link, visibility, idempotency, and expiry. Return-value explanation is correctly omitted because the output schema owns it.

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 lang, urls, view, title and description are already documented in the schema (including the title 'makes a page' note). The description restates the title/description-to-page relationship but adds no syntax, format, or bounds beyond what the schema provides, 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 first sentence names a specific verb and resource ('Makes a urlhub set from links') and immediately enumerates the artifacts produced: a short link, a page with each link's picture/title/description, and PNG/SVG QR codes. This is far more specific than a tautology, though it never names a sibling (featured_sets, preview_links, read_set) to disambiguate when another tool is the right pick.

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 gives concrete usage contexts — several links traveling together, sent to someone, opened later on a phone, printed as one QR code — and explains the title/no-title branching condition that selects the page vs short-link behavior. It stops short of explicit when-not guidance or routing to alternatives, so it is clear context rather than full when/why/when-not coverage.

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

All urlhub tools Inspect

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

Need Help?