Skip to main content
Glama
Sign In

The Bridge

by dev.thebridge
OverviewDiscussionsAdmin

List Short Links

list_short_links
Read-onlyIdempotent

List this workspace's tracking short links, newest first: short link, code, channel, detected platform and format, label, destination, and click counts (clicks by people, and botClicks by link previewers and scripts, counted apart). Links that share a code are the same content on different channels. Use create_short_link to make one.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many links to return (default 50, at most 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: results are ordered "newest first," click counts separate human clicks from botClicks, and links sharing a code represent the same content across channels. It does not discuss pagination behavior, but the limit parameter is documented in the schema.

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?

The description is front-loaded with the core action and scope, followed by precise details about returned fields and code-sharing semantics. Every sentence contributes useful information, and the creation alternative is cleanly appended without waste.

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?

There is no output schema, so the description carries the burden of explaining return values. It does so thoroughly by enumerating the returned fields, their ordering, and the distinction between clicks and botClicks. Combined with annotations and the fully described limit parameter, the definition is complete for an agent to invoke the tool correctly.

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 the single limit parameter is fully documented in the schema with its default and maximum. The description adds no additional parameter semantics, 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 states a specific verb and resource ("List this workspace's tracking short links"), and explicitly distinguishes this listing operation from the creation sibling by ending with "Use create_short_link to make one." An agent can immediately tell this is the read-only listing tool for short links.

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?

It clearly indicates when to use this tool for listing short links and explicitly points to create_short_link for creation. However, it does not describe any exclusion conditions or alternative listing tools, which is a minor gap given the straightforward read-only nature of the operation.

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

All The Bridge 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