QRStuff MCP Server

Create short link

create_short_link

Use this when the signed-in user wants a shorter, trackable web address for a link, with or without a QR code. Creates a QRStuff short link that redirects to the given URL and counts clicks. It is live and public immediately. Optional custom ending (slug); custom endings depend on the account. For a QR code of the short link, call generate_short_link_qrcode afterwards. Do not use it for a QR code that should open a URL directly (use generate_qr_code).

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": {
      "url": "<url>"
    },
    "name": "create_short_link"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The full web address to send people to, starting with https:// or http://.
`slug`	No	Optional custom ending, letters, numbers and hyphens, for example spring-sale. Leave empty for an automatic one.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes beyond the annotations by disclosing that the link becomes live and public immediately, that clicks are counted, and that custom endings are account-dependent. These are exactly the non-obvious operational facts an agent needs before mutating state in an open-world tool.

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?

Front-loads the use case, then behavior, then the optional parameter, then the two sibling redirects. Every sentence carries distinct information; nothing is padding.

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 an output schema present, the description needn't explain returns, and it is already complete on triggering conditions, exclusions, side effects, and the one conditional parameter. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: that the slug is optional, that it depends on the account, and that leaving it empty yields an automatic one. It does not restate the url parameter, which the schema already covers well.

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 concrete verb and resource ('Creates a QRStuff short link that redirects to the given URL and counts clicks') and explicitly distinguishes the artifact from a QR code. An agent can tell it apart from generate_qr_code and generate_short_link_qrcode without opening either schema.

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?

Gives the triggering condition ('when the signed-in user wants a shorter, trackable web address... with or without a QR code') plus two explicit exclusions routed to named alternatives: use generate_short_link_qrcode afterwards for a QR of the link, and generate_qr_code for a QR that opens a URL directly.

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

All QRStuff MCP Server 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?