List the account's short links with optional filters. Requires links:read scope.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | ||
| page | No | ||
| search | No | Matches slug, title, destination URL | |
| status | No | ||
| per_page | No | ||
| folder_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only mentions scope requirement. Missing behavioral traits such as pagination, ordering, rate limits, or filter interactions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise and front-loaded. Could be more structured but minimal waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Lacks output schema and annotations. Missing details on pagination defaults, result format, and error conditions for a listing tool with 6 parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is low (17%, only search described). Description says 'optional filters' but provides no additional meaning for parameters beyond basic names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool lists an account's short links with optional filters, using specific verb and resource. It distinguishes from sibling tools like get_link (single link) and create_link.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use versus alternatives like list_folders or list_tags. The scope requirement is noted but no comparative usage advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation (create, delete, update, list, etc.) on specific resources (links, folders, tags, analytics). No two tools have overlapping purposes.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_link, list_folders, and get_link_analytics. No deviations or mixed styles.
With 12 tools, the server covers the essential operations for a URL shortener (CRUD, analytics, QR codes, folders, tags) without being bloated or incomplete.
The tool set provides full lifecycle management for short links (create, read, update, delete, enable/disable), plus analytics, folders, tags, QR generation, and account usage. No obvious gaps.
