Skip to main content
Glama
Sign In

Linkbreakers MCP

by com.linkbreakers
OverviewDiscussionsAdmin

Get Link

links_get
Read-only

Get a specific link by its ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "links_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe ID of the link to retrieve (UUID)
includeNoList of related resources to include in the response. Supported values: "customDomain", "qrcodeDesign", "qrcodeSignedUrl", "tags", "pageTheme". Use "qrcodeSignedUrl" to fetch signed QR image URLs—they are omitted by default to keep requests fast.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this is a safe read, and the description adds nothing on top of it — no mention of behavior when the ID is unknown, whether includes affect latency, or what the payload looks like. With annotations carrying the safety profile, the description contributes no extra behavioral context.

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?

A single front-loaded sentence with zero waste. It is efficient but borders on under-specification given the tool's sibling set.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with full schema coverage and no output schema, the description is minimally adequate. It omits error behavior for missing IDs and any hint about the response shape, which would help an agent decide between this and links_list.

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 coverage is 100% and the include parameter is richly documented there, including the qrcodeSignedUrl performance caveat, so the description need not duplicate it. Baseline 3 applies since the description adds no parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (link) plus the lookup key (ID), which is enough to distinguish it from links_list, links_update, and links_delete. It stops short of explicitly naming those siblings or stating scope differences.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus links_list or the various links_create_* variants. The 'by its ID' phrasing implies a known-ID lookup, but the agent must infer that it should not be used for searching or listing.

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

All Linkbreakers MCP toolsInspect
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