PicSee Short Link
Server Details
PicSee URL shortener — shorten URLs, generate QR codes, view click analytics, manage links.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- PicSeeInc/picsee-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 1 of 1 tools scored.
Only one tool exists, so there is no ambiguity. The tool's purpose is clearly defined and distinct by default.
Single tool uses a consistent verb_noun pattern (create_short_link), which is clear and follows common conventions.
One tool is minimal but acceptable for a focused single-purpose service. However, many MCP servers for similar domains offer more tools, making this feel thin.
The server only provides creation of short links, lacking common operations like listing, updating, deleting, or analytics. This leaves significant gaps for typical URL shortening workflows.
Available Tools
1 toolcreate_short_linkAInspect
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. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for behavioral disclosure. It states that anonymous callers' domain value is ignored and that the response contains `picseeUrl`. However, it omits details on authentication, error handling, rate limits, or side effects like idempotency.
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 is compact: four sentences, no wasted words. It front-loads the primary purpose in the first sentence, then adds essential behavioral and response information. Every sentence adds value without 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?
The description covers the main purpose, required parameter, anonymous domain behavior, and the response key. However, it lacks explanation of error states (e.g., invalid URL format, duplicate slug), authentication requirements, or rate limits. For a tool with 5 parameters and no output schema, more context is expected to enable correct invocation.
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% (all 5 parameters documented in schema), but the description adds substantial value: it clarifies that `domain` is ignored for anonymous callers, provides best-practice guidance for `externalId` to default to the agent's product name, explains the conflict error code for `encodeId`, and mentions that `utm` can be cleared with `null` on edit. This enriches the schema definitions significantly.
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 'Create a new PicSee short link from a destination URL.' It specifies the action (create), the resource (short link), and the service (PicSee). The required parameter is identified, and no sibling tools exist, so no differentiation is needed.
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 marks `url` as required and notes that all other fields are optional. It provides a specific usage caveat for anonymous callers regarding domain. However, it does not specify when to avoid using this tool or mention alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!