QRStuff MCP Server

Create link page

create_link_page

Use this when the user wants a landing page or "link in bio" page: a simple hosted mobile page with a title and several links. Creates a draft in their account and returns an editor link. It is not public until published with update_link_page. Does not make a QR code (use create_launchpad_qrcode for page, short link and QR code in one step). Do not use it for a business card or menu.

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": {
      "title": "<title>"
    },
    "name": "create_link_page"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Page title shown at the top of the landing page.
`project_id`	No	Optional project ID from `list_projects` to file it in.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the generic mutation profile (not read-only, not idempotent, not destructive). The description adds the behaviorally decisive facts: the resource is created as a draft, is not public until update_link_page publishes it, and an editor link is returned — all of which change how an agent sequences follow-up calls.

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?

Four sentences, front-loaded with the trigger condition, then lifecycle, then alternatives/exclusions. Every sentence carries distinct information with no restatement of the title or annotations.

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?

With an output schema present, return values need not be explained, and the description still covers the draft lifecycle and the publish path. Minor gaps remain (e.g., limits on number of links, what project_id defaulting to null means in practice), but nothing that would cause a mis-call.

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%, and both parameters (title, project_id) are documented in the schema including the list_projects reference. The description adds no format, length, or defaulting guidance beyond what the schema already states, so the baseline 3 applies.

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 draft... landing page with a title and several links') and pins down the artifact well enough that an agent knows exactly what is produced. It also names what it is not by pointing at create_launchpad_qrcode and excluding business cards/menus, distinguishing it from the many create_* siblings.

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 an explicit trigger ('when the user wants a landing page or "link in bio" page'), an explicit alternative for the combined page+short-link+QR case, and explicit exclusions (business card, menu). Both the when and the when-not are covered with named siblings.

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?