QRStuff MCP Server

Create landing page QR code

create_launchpad_qrcode

Use this when the user wants a new landing page and a QR code that opens it in one step. Creates and publishes the page, a short link and a dynamic QR code, so confirm the title with the user first. Do not use it to edit an existing page.

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_launchpad_qrcode"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Page title shown at the top of the landing page. Confirm it with the user.
`qr_name`	No	Optional name for the QR code in the dashboard.	Landing Page QR Code
`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.3/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world write operation. The description adds useful behavioral context by disclosing that it publishes a page and creates a short link and dynamic QR code, and it tells the agent to confirm the title with the user first.

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?

The description is three efficient sentences, front-loaded with the primary use case and followed by the side effects and exclusion. Every sentence carries actionable guidance.

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?

Given the high schema coverage, existing annotations, and an output schema, the description provides enough context for correct invocation. It explains the composite creation behavior, the need to confirm the title, and when not to use the tool.

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 three parameters are already documented in the input schema. The description reinforces the title confirmation requirement but does not add meaning beyond the schema for qr_name or project_id.

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?

The description states a specific composite action: creating and publishing a landing page, short link, and dynamic QR code in one step. It also distinguishes the tool from editing an existing page and implicitly from sibling tools that create only one resource at a time.

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 a clear use case ('when the user wants a new landing page and a QR code... in one step') and an explicit exclusion ('Do not use it to edit an existing page'). It does not name specific sibling alternatives, such as create_link_page or generate_link_page_qrcode, so it stops short of fully explicit alternative routing.

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?