Affilio Link Tools

Generate Qr

generate_qr

Generate a branded QR code PNG image for any URL with full visual customization.

Returns a base64-encoded PNG you can embed directly in a web page (<img src="data:image/png;base64,..."/>), email, or document. Color, transparency, and dot style are all configurable.

Use this tool when the user needs to:

Create a scannable QR code for a URL
Generate print-ready QR codes for marketing materials, packaging, or flyers
Embed a QR code in an email or web page
Create a branded QR code matching their visual identity (custom colors, transparent background)

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": "generate_qr"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Full URL to encode in the QR code. Must be a valid HTTP/HTTPS URL. Example: https://mcp.affilio.link/r/abc1234
`color`	No	Foreground/dot color as a CSS hex string. Examples: #000000 (black), #1A73E8 (Google blue), #FF5722 (deep orange). Default: #000000 (black).	#000000
`rounded`	No	When true, uses rounded/circular dot style instead of hard square pixels. Produces a modern, visually appealing QR code. Default: true.
`transparent`	No	When true, the QR code background is rendered transparent (PNG alpha channel). Overrides background_color. Ideal for overlaying on branded backgrounds. Default: true.
`background_color`	No	Background fill color as a CSS hex string. Ignored when transparent=true. Examples: #FFFFFF (white), #F5F5F5 (light grey). Default: #FFFFFF (white).	#FFFFFF

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 13, 2026

changedInput schema / properties / url / description

Previous value: -"Full URL to encode in the QR code. Must be a valid HTTP/HTTPS URL. Example: https://affilio.link/abc123"New value: +"Full URL to encode in the QR code. Must be a valid HTTP/HTTPS URL. Example: https://mcp.affilio.link/r/abc1234"

Changed5 schema fields changedJun 26, 2026

addedInput schema / properties / background_color / description

Added value: +"Background fill color as a CSS hex string. Ignored when transparent=true. Examples: #FFFFFF (white), #F5F5F5 (light grey). Default: #FFFFFF (white)."

addedInput schema / properties / color / description

Added value: +"Foreground/dot color as a CSS hex string. Examples: #000000 (black), #1A73E8 (Google blue), #FF5722 (deep orange). Default: #000000 (black)."

addedInput schema / properties / rounded / description

Added value: +"When true, uses rounded/circular dot style instead of hard square pixels. Produces a modern, visually appealing QR code. Default: true."

addedInput schema / properties / transparent / description

Added value: +"When true, the QR code background is rendered transparent (PNG alpha channel). Overrides background_color. Ideal for overlaying on branded backgrounds. Default: true."

addedInput schema / properties / url / description

Added value: +"Full URL to encode in the QR code. Must be a valid HTTP/HTTPS URL. Example: https://affilio.link/abc123"

First observedApr 28, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description does carry useful behavioral weight: it discloses the base64-PNG return format and the embed pattern. However, it says nothing about authentication, rate limits, failure modes for invalid URLs, or image dimensions, so the safety/operational profile is only partially covered.

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 first sentence front-loads the core action and output, followed by return-format details and a scannable bullet list. The bullets are slightly redundant with the opening sentence but remain useful and short; no filler paragraphs.

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?

An output schema exists, so return values need no exposition, and the schema fully documents the five parameters. The description is complete for invocation purposes, with only tangential gaps (auth, limits, image size) remaining.

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 each parameter has an example, default, and interaction note (transparent overrides background_color). The description only restates the categories as "color, transparency, and dot style" without adding syntax, constraints, or edge-case guidance beyond the schema, so 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 specific verb (Generate) and resource (a branded QR code PNG for a URL) with the output format named up front. It is clearly distinguishable from siblings like shorten_url or check_url, since none of them produce an image artifact.

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?

Provides four explicit use-case bullets (scannable QR, print-ready marketing, email/web embedding, branded visual identity), giving a clear picture of when to reach for it. It stops short of saying when NOT to use it or pointing to an alternative, so it lands just below the top score.

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

All Affilio Link Tools 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?