shorttext
Server Details
Paste short text, get a shareable URL. Read any by slug; create with an API key.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.5/5 across 2 of 2 tools scored.
The two tools have entirely distinct purposes: one creates short texts, the other reads them by slug. No overlap.
Both tools follow the verb_noun pattern (create_shorttext, read_shorttext), making them predictable and consistent.
With only two tools covering the core create/read operations, the count is perfectly suited to the server's minimalist short text sharing scope.
The set covers the essential create and read operations. Missing delete or update tools are minor gaps given the domain's simplicity.
Available Tools
2 toolscreate_shorttextAInspect
Create a new shortText and get a shareable shorttext.com URL back. Markdown is supported. Requires an API key in the request Authorization header (Bearer st_live_…, request one from api@shorttext.com) — without it, creation is rejected (reading stays open to everyone).
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | The text content (Markdown supported, max 30,000 chars). | |
| expiry | No | Defaults to "never". | |
| password | No | Required when visibility is "private". | |
| visibility | No | Defaults to "public". "private" requires a password. | |
| burnAfterRead | No | Delete after the first view. Defaults to false. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, description covers auth requirement, rejection behavior, open reading, and Markdown support. Lacks mention of rate limits or error details, but adds essential context.
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 sentences, front-loaded with main action. No fluff, every sentence adds information.
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?
Covers creation, output (shareable URL), auth, Markdown. No output schema, but description implies return value. Could mention pagination or limits, but sufficient for this tool.
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%, but description adds value: body max length (30k chars), Markdown support, and clarifies password required for private visibility. Also explains that API key is needed (not in schema).
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?
Clearly states 'Create a new shortText and get a shareable shorttext.com URL back.' Specific verb, resource, and outcome. Distinguishes from sibling read_shorttext.
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?
Explicitly requires API key for creation, and notes that reading is open to everyone. Provides clear when-to-use vs. alternative (read_shorttext).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
read_shorttextAInspect
Fetch a shortText by its slug (the id in a shorttext.com/{slug} URL). Returns the text body and metadata. Public and unlisted shortTexts are open; private ones need a password. Reading a burn-after-read shortText consumes it.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The shortText slug, e.g. "abc12345". | |
| password | No | Password — required only for private shortTexts. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Discloses that burn-after-read shortTexts are consumed on reading, and password is needed for private ones.
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?
Two sentences covering purpose, access types, and burn-after-read behavior. No wasted words.
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?
For a simple tool with 2 params and no output schema, description adequately states return (text body and metadata) and access rules.
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 3. Description adds context: slug is from URL, password explains when required, adding value beyond schema.
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 uses specific verb 'Fetch' and resource 'shortText by its slug', clearly distinguishing it from sibling tool 'create_shorttext'.
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?
Explains when to use (fetching), conditions for public/unlisted/private/burn-after-read, but does not explicitly state when not to use or list alternatives beyond the sibling name.
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!