Skip to main content
Glama
enesjakozh
Talismanic

URL Shortener MCP

by Talismanic
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

URL Shortener MCP Tool

This project provides a simple URL shortening tool using the CleanURI API and is designed to run as a FastMCP server tool.

✨ Features

  • Shortens any given URL using the CleanURI API.

  • Exposes the functionality as a tool via FastMCP.

  • Includes proper error handling and response validation.

  • Designed to run via stdio transport for integration with agent or tool-based systems.

Related MCP server: MCP Website Fetcher

🚀 Usage

1. Requirements

  • Python 3.10+

  • httpx

  • fastmcp

2. Installation

Installing via Smithery

To install URL Shortener Tool for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @Talismanic/cleanuri-url-shortener-mcp --client claude

Manual Installation

uv add httpx 'mcp[cli]'

Docker Installation:

docker build -t url-shortener .

3. Running

uv run main.py

For docker based use, we dont need to do anything here.

4. Adding in Claude Desktop

With the uv

{
  "mcpServers": {
    "url-shortener": {
      "command": "/Users/{userName}/.local/bin/uv",
      "args": [
        "--directory",
        "{path_to_repo}/cleanuri-url-shortener-mcp",
        "run",
        "main.py"
      ]
    }
  }
}

With Docker

{
  "mcpServers": {
    "url-shortener": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--init",
        "-e",
        "DOCKER_CONTAINER=true",
        "url-shortener"
      ]
    }
  }
}

Available Tools

1 tool
shortenB

Shorten a URL using the cleanuri API.

Args:
    original_url: The URL to shorten.
ParametersJSON Schema
NameRequiredDescriptionDefault
original_urlYes

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a URL shortening operation but doesn't disclose behavioral traits like whether this requires authentication, rate limits, what happens with invalid URLs, or what the output format looks like. The mention of 'cleanuri API' adds minimal context but lacks operational details.

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 appropriately sized and front-loaded: the first sentence states the core purpose, and the second provides parameter documentation. There's zero wasted text, and the structure is clear with a brief introduction followed by args.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (single parameter, no annotations, no output schema), the description is minimally adequate. It covers the basic purpose and parameter, but lacks important context like output format, error handling, or API constraints. Without an output schema, the description should ideally hint at what gets returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explicitly documents the single parameter 'original_url' with a clear explanation ('The URL to shorten'), which adds meaningful semantics beyond the bare schema. However, it doesn't provide format examples or validation rules (e.g., must be a valid HTTP URL).

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 tool's purpose with a specific verb ('shorten') and resource ('URL'), and identifies the external service ('cleanuri API'). It doesn't need to distinguish from siblings since there are none. However, it could be slightly more specific about what type of shortening service cleanuri provides.

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 provides no guidance on when to use this tool versus alternatives (though there are no sibling tools). It doesn't mention prerequisites, rate limits, or any constraints. The only usage context is the API name, which is insufficient for proper guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedshorten
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'shorten' has a single, clear purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'shorten' follows a clear verb-based pattern appropriate for its function, with no other tools to compare against for inconsistency.

Tool Count2/5

A single tool for a URL shortener server is too few for the apparent scope, as it only covers shortening URLs without any complementary operations like retrieving, updating, deleting, or listing shortened URLs. This minimal set limits functionality and may cause agent failures in broader workflows.

Completeness2/5

The tool surface is severely incomplete for a URL shortener domain. While 'shorten' allows creation, there are no tools for retrieving, updating, deleting, or managing shortened URLs (e.g., get_url, list_urls, delete_url), creating significant gaps that will hinder agent performance in typical use cases.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Rebrandly MCP by rebrandly

    Rebrandly MCPofficial

    rebrandly
    A
    license
    Not graded
    quality
    F
    maintenance
    This project implements a simple MCP server in Go that exposes a single tool (create_short_link) to generate short URLs using the Rebrandly API.
    MIT

  • MCP Website Fetcher

    electrocucaracha
    F
    license
    Not graded
    quality
    F
    maintenance
    A lightweight MCP server implementation that provides a simple tool for fetching website content, demonstrating how tools can be exposed and interacted with using the MCP protocol.
    -

  • ShortURLMCP

    AceDataCloud
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that enables users to shorten long URLs into permanent, shareable links using the AceDataCloud API. It supports both single and batch URL shortening directly within MCP-compatible clients like Claude and VS Code.
    4
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Talismanic/cleanuri-url-shortener-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server