list_urlsList your short links, newest first, with click counts. Use it to browse or to find a link's code; for one known code use get_url, and for clicks over time get_url_stats. Returns one page; use page to see more.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, starting at 1. | |
| limit | No | Links per page. |
| Name | Required | Description | Default |
|---|---|---|---|
| page | Yes | ||
| limit | Yes | ||
| links | Yes | ||
| total | Yes | ||
| hasMore | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / links / items / properties / appLinkAdded value: +{
+ "description": "App links only: where iOS and Android go, and the page other devices see.",
+ "properties": {
+ "androidUrl": {
+ "type": "string"
+ },
+ "appName": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "iconUrl": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "iosUrl": {
+ "type": "string"
+ },
+ "otherwise": {
+ "enum": [
+ "mobile_only",
+ "store_links",
+ "store_badges"
+ ],
+ "type": "string"
+ },
+ "qrCodeUrl": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "iosUrl",
+ "androidUrl",
+ "otherwise"
+ ],
+ "type": "object"
+}Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "hasMore": {
+ "type": "boolean"
+ },
+ "limit": {
+ "type": "integer"
+ },
+ "links": {
+ "items": {
+ "properties": {
+ "active": {
+ "type": "boolean"
+ },
+ "clickCount": {
+ "type": "integer"
+ },
+ "createdDate": {
+ "description": "ISO-8601 instant.",
+ "type": "string"
+ },
+ "expiresDate": {
+ "description": "ISO-8601 instant; null when the link never expires.",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "fallbackUrl": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "isCustomCode": {
+ "type": "boolean"
+ },
+ "originalUrl": {
+ "type": "string"
+ },
+ "shortCode": {
+ "type": "string"
+ },
+ "shortUrl": {
+ "description": "Ready-to-share short link.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "shortUrl",
+ "shortCode",
+ "originalUrl"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "page": {
+ "type": "integer"
+ },
+ "total": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "links",
+ "page",
+ "limit",
+ "total",
+ "hasMore"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: results are ordered newest first, include click counts, and are paginated ("Returns one page; use page to see more"). It does not mention auth requirements or a maximum page depth, which keeps it from a 5.
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?
Three short sentences, front-loaded with purpose and immediately followed by routing and pagination constraints. Every sentence carries distinct information with no repetition of the name or title.
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?
An output schema exists, so return values need not be described, and the description still covers the key shape (paged list with click counts). Pagination, ordering, and sibling routing are all addressed, leaving nothing an agent needs in order to call this correctly.
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 100%, so baseline is 3; the description earns a bump by explaining the intent of the page parameter in context ("Returns one page; use page to see more"), which tells the agent why pagination exists, not just its type. The limit parameter is left entirely to the schema, so it is not a full 5.
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?
States a specific verb and resource ("List your short links") plus scope details an agent cannot get from the name: newest-first ordering and click counts included. It explicitly names the sibling tools get_url and get_url_stats as different operations, so the agent can discriminate without opening schemas.
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?
Gives explicit use cases ("browse or to find a link's code") and explicit alternatives with the condition that selects them: "for one known code use get_url, and for clicks over time get_url_stats." Nothing is left to inference about routing.
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.