Skip to main content
Glama
Sign In

Linkbreakers MCP

by com.linkbreakers
OverviewDiscussionsAdmin

List Links

links_list
Read-only

List all links in the workspace with optional filtering by tags and search.

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": {
      "pageSize": "<pageSize>"
    },
    "name": "links_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags to filter links by (matches links containing any of the provided tags)
viewNoView mode for the link listing. LINK_VIEW_UNSPECIFIED (default): returns all links regardless of directory. LINK_VIEW_DIRECTORY: scoped to a directory; use directory_id to pick which one, or omit directory_id to get root-level links (not in any directory).
searchNoSearch query to filter links by name or shortlink
sortByNoField to sort links by (defaults to updated_at if not specified)
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.
pageSizeYesThe maximum number of links to return.
pageTokenNoThe token for retrieving the next page of results If not provided, the first page of results will be returned
directoryIdNoThe directory to scope to when view is LINK_VIEW_DIRECTORY. Ignored when view is LINK_VIEW_UNSPECIFIED (all links).
sortDirectionNoSort direction (defaults to descending if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, and the description confirms read-only listing without adding much beyond that. It omits pagination behavior and the include-driven response variations, which the schema documents 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?

A single efficient sentence that front-loads the action and resource with zero filler.

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?

For a read-only list tool with 9 fully described parameters and no output schema, the description is adequate; pagination and include semantics live in the schema. Minor gap: it doesn't flag that pageToken is needed for multi-page enumeration.

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 tags and search is fully documented in structured data. The description merely echoes 'filtering by tags and search', adding no syntax or default information 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 and resource (list links) plus scope (workspace) and the filtering axes (tags, search). An agent can distinguish it from links_get/links_create, though it doesn't explicitly name a sibling to avoid.

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

Usage Guidelines3/5

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

Implies use for enumerating links with optional filtering, but never says when to prefer links_get, when to paginate, or how large a page to request. Usage is inferable but not guided.

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