QRStuff MCP Server

Get short link clicks

get_short_link_clicks

Read-onlyIdempotent

Use this when the user asks how many times a short link was clicked, or where, when or on what device. Group by individual click, date, country, region or device, with an optional date range. For scans of a QR code use get_qrcode_scans. Read-only.

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": {
      "idshorturl": "<idshorturl>"
    },
    "name": "get_short_link_clicks"
  }
}

Input Schema

Name	Required	Description	Default
`country`	No	Two-letter country code. Required when group_by is region.
`end_date`	No	End of the period, YYYY-MM-DD. Leave empty for today.
`group_by`	No	scan for individual clicks, or date, country, region or device for totals.	scan
`per_page`	No	Results per page, 5 to 100.
`idshorturl`	Yes	Short link ID from `list_short_links`. Never guess an ID.
`start_date`	No	Start of the period, YYYY-MM-DD. Leave empty for the last 30 days.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the trailing 'Read-only' merely restates structured data. The description adds no behavioral context beyond that — no mention of the default 30-day window, pagination behavior, or that the ID must come from `list_short_links` — which the schema carries instead.

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?

Three short sentences with zero filler: trigger first, capability second, disambiguation third. Every clause carries routing or scoping information.

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 no explanation, and the fully-documented schema covers defaults and the ID-provenance warning. The description covers purpose, alternative and safety, leaving only minor gaps like the implicit 30-day default window.

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 every parameter including `group_by` values, the country/region dependency, date format and per_page bounds is already documented. The description only paraphrases the grouping options in prose, adding no syntax or constraint detail beyond the schema, 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 specific verb and resource ('how many times a short link was clicked') plus the analytic dimensions it supports (where, when, device). It explicitly distinguishes itself from the QR-scan sibling `get_qrcode_scans`, so an agent can route between the two 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?

Opens with an explicit trigger condition ('Use this when the user asks how many times a short link was clicked'), then names the alternative tool and the condition that selects it ('For scans of a QR code use `get_qrcode_scans`'). Nothing about when to reach for this tool is left to inference.

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?