renamed-to
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENAMED_TOKEN | No | Fallback token for renamed.to. | |
| RENAMED_API_KEY | No | Your renamed.to API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| renameA | Rename files using AI content analysis. Sends files to the renamed.to API which analyzes content and returns intelligent filenames. |
| pdf_splitA | Split PDFs by content or topic using AI, by bookmarks, or by page ranges. Sends the PDF to the renamed.to API for processing. |
| watchB | Watch a directory for new files and auto-process them using rename or pdf-split. |
| statusA | Check authentication status and API connectivity for the renamed.to service. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: pdf_split splits PDFs, rename renames files, watch automates processing, and status checks connectivity. There is no overlapping functionality or ambiguity in which tool to use for a given task.
The names follow a loose verb-centric pattern, but 'pdf_split' uses noun-verb order while 'rename', 'watch', and 'status' are single verbs/nouns. This creates a minor inconsistency in style that could be improved by renaming to 'split_pdf' or similar.
With only four tools, the server is tightly scoped to its core purpose of AI-powered file renaming and splitting, plus automation and status checking. Each tool is necessary and there are no redundant or superfluous entries.
The set covers the primary workflows: renaming, splitting, automating via watch, and checking authentication. A minor gap might be the absence of a direct upload/download or batch management tool, but the core lifecycle is fully supported.