Official PicSee MCP server for short links, link management, click analytics, and optional OAuth.
Scored across 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly distinct from any other.
The single tool name 'create_short_link' follows a consistent verb_noun pattern, which is clear and predictable.
Only one tool is provided for a short link service, which feels thin. Typically, such a service would benefit from additional tools like listing or deleting links.
The tool only supports creation of short links. There are no tools for reading, updating, or deleting links, leaving significant gaps for typical use cases.
Create a new PicSee short link from a destination URL. url is required; every other field is optional. Anonymous callers are pinned to the pse.is domain — any domain value supplied is ignored. The response contains picseeUrl, the shortened link ready to share.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Destination URL the short link should redirect to. Required. | |
| utm | No | UTM parameters appended to the destination URL. Pass `null` on edit to clear all previously set UTM values. | |
| domain | No | Domain to host the short link on (e.g. `pse.is` or one of the BSDs from `get_my_domains`). Falls back to the account default when omitted or invalid. | |
| encodeId | No | Custom slug (3-90 chars; English letters, digits, `_`, `-`, or Chinese). Must be globally unique on PicSee — conflicts return `PUB00503`. Omit to let PicSee auto-generate. | |
| externalId | No | Free-form identifier (1-100 chars) for grouping / attributing links. Surfaces in `list_short_links` filters and `get_api_usage_by_external_id`. When the user has not specified a value, you (the calling AI agent) SHOULD default this to your own product name so the account owner can attribute API usage back to the agent that created the link — e.g. `Claude Code`, `Codex`, `Cursor`, `ChatGPT`, `Gemini CLI`, `Copilot`. Use the canonical product name only; do not include version numbers or session IDs. If the user explicitly provides an `externalId`, always honor their value instead. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose all behavioral traits. It mentions the response contains 'picseeUrl' and that anonymous callers have the domain ignored. However, it does not mention error conditions (e.g., encodeId conflict), rate limits, or authentication requirements beyond the anonymous note.
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?
The description consists of three concise sentences. The first states the core action, the second clarifies requirement, and the third adds important constraint. Every sentence adds value with no redundancy.
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?
Given 5 parameters (1 required), 100% schema coverage, no output schema, and no siblings, the description covers the main purpose and parameter usage well. It explains the core output ('picseeUrl'). However, it could be enhanced by mentioning the response structure or common error codes to be fully complete.
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. However, the description adds significant value beyond the schema: it states that 'url' is required and all others optional (schema has required array but not in param description), gives specific guidance on 'externalId' about defaulting to product name, and notes domain behavior for anonymous callers. This extra context is highly helpful for correct invocation.
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?
The description clearly states the action ('Create') and the resource ('PicSee short link') with the source ('from a destination URL'). It is specific and leaves no ambiguity about the tool's purpose.
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?
The description explicitly says that 'url' is required and all other fields are optional. It also gives a special guideline for 'externalId' instructing the AI to default it to the product name when not provided. Anonymous callers are warned about domain suppression. This provides clear when-to-use and when-not-to-use instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
create_short_linkOfficial in.bio MCP server: shorten URLs, styled QR codes, and click analytics. No API key needed.
The official Planning Center MCP server for interacting with your ministry's data.
The official MCP Server for the Mux API
Add one secure layer between your agents and this server.
