Skip to main content
Glama

ShareCut QR & Short Links

by io.github.LucaRSdeCo

Delete a link

delete_link

Permanently delete a link and its click history. Every QR code and shared copy pointing at it stops working immediately, and the short code is released. There is no undo. Prefer update_link when the goal is to send the link somewhere else. Requires a ShareCut API key (Business plan).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkYesThe link, given either as its short code (the part after sharecut.site/) or as the id returned when it was created. A full ShareCut URL is accepted too.
confirmYesMust be true. Deletion is permanent and breaks every printed copy.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses irreversibility, cascading breakage of QR codes and shared copies, short-code release, and explicitly notes there is no undo, plus the access/auth constraint.

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?

Every sentence earns its place: destructive effect, cascading impact, irreversibility, preferred alternative, and access requirement. The core action is front-loaded, and there is no filler or repetition.

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?

For a two-parameter destructive tool with no annotations and no output schema, the description covers the operation's effect, side effects, permissions, irreversibility, and the correct alternative. Nothing essential for selecting or invoking the tool is missing.

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%, with both link and confirm already well described. The tool description adds behavioral context but no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 opens with a specific verb and object — 'Permanently delete a link and its click history' — and follows with concrete effects: QR codes and shared copies stop working and the short code is released. It clearly distinguishes the tool from update_link, the nearest sibling alternative.

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?

Explicitly instructs the agent to prefer update_link when the goal is to send the link somewhere else, which is a clear when-not-to-use signal. It also states the API key and Business plan requirement, giving the agent actionable conditions for invocation.

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

All ShareCut QR & Short Links toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with strong descriptions, but three tools (create_qr, shorten_url, get_link_qr) can all produce a QR code, which could cause misselection without careful reading. The public-versus-account split and singular-versus-bulk variants are otherwise well separated.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: check_, create_, delete_, expand_, get_, list_, shorten_, update_. Composite names like get_link_analytics and shorten_urls_bulk extend the pattern predictably without mixing conventions.

Tool Count5/5

With 12 tools, the server is well-scoped for a QR and short-link management API. It includes public query tools, full CRUD for links, bulk creation, QR retrieval, analytics, and account status, with no unnecessary duplication.

Completeness4/5

The core link lifecycle is covered: create, read, list, update, delete, plus QR generation, analytics, and account info. Minor gaps exist around non-link resources like link-in-bio pages or restaurant menus that are only referenced by list_links, and there is no API to edit QR artwork directly, but these are peripheral to the stated purpose.

Resources