Remote MCP server for parsing public single-post video and image links across 11 platforms. Requires an Easydown API token and paid credits. Setup: https://easydown.org/mcp
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between competing tools. The single tool's purpose — returning downloadable media URLs from a supported public post URL — is unambiguous and self-contained.
The name parse_media_url follows a clean verb_noun snake_case convention, and the verb accurately reflects the operation. With only one name there is no risk of convention drift, and it reads predictably.
A single tool is thin even for a narrow domain; everything — ten-plus platform URL families, credit pricing, and error semantics — is packed into one oversized description. Companion tools (e.g. checking credit balance or supported platforms) would make the surface easier to work with.
The stated purpose (parsing supported post URLs into downloadable media URLs) is covered exhaustively across TikTok, YouTube, Xiaohongshu, Bilibili, Weibo, and more, including pricing behavior. Minor gaps remain: no way to query credit balance or account status, and no batch or actual-fetch operation for agents to proceed past the returned URLs.
Return every downloadable image, video, and audio URL exposed by a supported public single-post URL. Supported URL families: TikTok video/photo/t and vm/vt share links; Douyin video/note/slides/share/detail, vid/modal_id, direct play/playwm, and direct media links; Toutiao /video and m.toutiao.com/is links; YouTube watch, /v, youtu.be, Shorts, live replay, and Google redirect or imgres links that wrap supported YouTube URLs; X/Twitter status links; Instagram post, Reel, user-path post/Reel, mobile, Story, embed, and share links; Threads threads.com/threads.net post, /media, and share redirect links, including linked inline media and available WEBP animated-image attachments; Xiaohongshu xhslink.com/o, xhslink.cn/o, xiaohongshu.com note, and RedNote explore/discovery links; Bilibili BV/av, b23.tv, bangumi/cheese, and list bvid links; Kuaishou/Kwai/Gifshow/Chenzhongtech single-work, /f, photoId/photo_id, share links, and copied Markdown text containing or repeating the same supported short URL; Weibo desktop, mobile status/detail, t.cn/visitor, layerid, tv/show, h5.video show, mapp.api.weibo.cn/fx, and video.weibo.com fid links. Downloadable results cost 1 credit by default. YouTube costs 3 credits, Threads and Kuaishou cost 2 credits, and Xiaohongshu / RedNote costs 10 credits. A confirmed processing cost followed by a clear content restriction is charged at the same platform rate. Unsupported URLs, authentication errors, temporary failures, and unconfirmed empty results are not charged.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Supported URL families: TikTok video/photo/t and vm/vt share links; Douyin video/note/slides/share/detail, vid/modal_id, direct play/playwm, and direct media links; Toutiao /video and m.toutiao.com/is links; YouTube watch, /v, youtu.be, Shorts, live replay, and Google redirect or imgres links that wrap supported YouTube URLs; X/Twitter status links; Instagram post, Reel, user-path post/Reel, mobile, Story, embed, and share links; Threads threads.com/threads.net post, /media, and share redirect links, including linked inline media and available WEBP animated-image attachments; Xiaohongshu xhslink.com/o, xhslink.cn/o, xiaohongshu.com note, and RedNote explore/discovery links; Bilibili BV/av, b23.tv, bangumi/cheese, and list bvid links; Kuaishou/Kwai/Gifshow/Chenzhongtech single-work, /f, photoId/photo_id, share links, and copied Markdown text containing or repeating the same supported short URL; Weibo desktop, mobile status/detail, t.cn/visitor, layerid, tv/show, h5.video show, mapp.api.weibo.cn/fx, and video.weibo.com fid links. Submit the complete public URL. |
| Name | Required | Description |
|---|---|---|
| msg | Yes | |
| code | No | |
| data | Yes | |
| status | Yes | |
| billing | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare openWorldHint, non-destructive, non-idempotent, and readOnlyHint=false. The description adds substantial behavioral detail beyond them: default 1-credit cost, platform-specific credit rates, and precise conditions under which charges are or are not incurred. The main omission is any note on authentication requirements or rate limits.
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 first sentence is front-loaded and effective, but the description then repeats the long URL-family list already present in the schema and continues into pricing details. It is substantially longer than necessary and duplicates structured data rather than concentrating on value-add 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?
The tool has an output schema, full parameter schema coverage, and annotations covering safety and openness. The description completes the picture with supported input families, credit pricing, and charge-exemption rules, so an agent has enough information to call it correctly without relying on omitted return-value explanations.
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 the single URL parameter is already fully documented in the schema. The description duplicates the same supported URL-family text rather than adding new parameter meaning, so the baseline of 3 applies.
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 first sentence states a specific verb and resource: return downloadable image, video, and audio URLs from a supported public single-post URL. It also scopes the tool to public single-post inputs and enumerates supported URL families, so an agent can identify the operation without ambiguity.
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 gives clear applicability through the extensive supported URL-family list and states that unsupported URLs are not charged. It lacks explicit when-not-to-use guidance beyond unsupported URLs, but there are no sibling tools to route between, so the usage context is still strong.
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.
parse_media_url
Add one secure layer between your agents and this server.