ParseJet - Universal File & URL Parser
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARSEJET_API_KEY | No | Set the PARSEJET_API_KEY environment variable to authenticate. Without it, the server works anonymously with a limit of 3 requests per day. |
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 |
|---|---|
| parse_urlB | Parse any URL (web page, YouTube video, PDF link, etc.) and extract its content as text or markdown. |
| parse_fileB | Parse a local file (PDF, DOCX, image, etc.) by uploading it to ParseJet and extracting its content. |
| get_youtube_transcriptB | Get the transcript of a YouTube video, optionally in a specific language. |
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 3 tools
Tools mostly distinct: parse_file handles local files, parse_url handles any URL, get_youtube_transcript is specialized for YouTube transcripts. There is slight overlap between get_youtube_transcript and parse_url for YouTube videos, but descriptions clarify different intents.
Two tools follow a parse_* pattern, while get_youtube_transcript breaks consistency with a get_ prefix. This is a minor deviation but still understandable.
3 tools for a 'Universal File & URL Parser' feels slightly thin but not unreasonable. The scope is covered by the two parse tools, with the transcript tool as an additional feature.
Core functionality (parsing local files and URLs) is covered. Missing explicit tools for structured data parsing (e.g., JSON, XML) but the parse_file and parse_url tools claim broad support. Minor gaps but adequate for common tasks.