Surli MCP

create_short_link

Shorten a destination URL via Surli and return short link and stats.

Input Schema

TableJSON Schema

Name	Required	Description
`alias`	No	Optional custom slug/alias for the short URL
`title`	No	Optional display title or tag for the link
`destination_url`	Yes	The full target destination URL to shorten (e.g. https://example.com)

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	No	Current account tariff plan (e.g. limited, unlimited)
`used`	No	Number of short links used in the current plan period
`limit`	No	Total short link quota for the plan period (-1 = unlimited)
`remaining`	No	Number of short links remaining (-1 = unlimited)
`short_url`	Yes	The newly created short URL
`user_message`	No	Human-readable status message
`dashboard_url`	No	Link to manage this short URL in the Surli dashboard
`destination_url`	Yes	The destination URL the short link points to

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "dashboard_url": {
+      "description": "Link to manage this short URL in the Surli dashboard",
+      "type": "string"
+    },
+    "destination_url": {
+      "description": "The destination URL the short link points to",
+      "type": "string"
+    },
+    "limit": {
+      "description": "Total short link quota for the plan period (-1 = unlimited)",
+      "type": "integer"
+    },
+    "plan": {
+      "description": "Current account tariff plan (e.g. limited, unlimited)",
+      "type": "string"
+    },
+    "remaining": {
+      "description": "Number of short links remaining (-1 = unlimited)",
+      "type": "integer"
+    },
+    "short_url": {
+      "description": "The newly created short URL",
+      "type": "string"
+    },
+    "used": {
+      "description": "Number of short links used in the current plan period",
+      "type": "integer"
+    },
+    "user_message": {
+      "description": "Human-readable status message",
+      "type": "string"
+    }
+  },
+  "required": [
+    "short_url",
+    "destination_url"
+  ],
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the creation behavior is implied. The description adds that the operation goes through Surli and returns 'short link and stats,' which is useful, but it does not disclose potential side effects, alias availability constraints, or external-service limits.

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?

One sentence with no wasted words, and the main purpose and return value are both included. It is front-loaded and easy to parse.

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 simple creation tool with a full input schema, optional parameters, and an output schema, the description covers the essential purpose and return behavior. It is not an exhaustive explanation, but the missing details are already available in structured fields.

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?

The input schema has 100% description coverage for all three parameters, so the schema carries the semantic load. The description does not add any significant parameter-level meaning, making the baseline 3 appropriate.

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?

The description clearly states the action ('Shorten a destination URL') and the resource ('via Surli'), and implies a creation operation rather than retrieval or update. It does not explicitly name its sibling tools, but the verb and resource are specific enough to avoid confusion.

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?

The description gives no explicit guidance about when to use this tool instead of get_short_link, update_alias, or update_destination. The operation is inferable, but no context or exclusion criteria are provided.

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

All Surli MCP tools Inspect

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

Need Help?