---
name: sharelink-jobs
description: "Step-by-step job recipes for the Share Link Resolver MCP server: Resolve a share link; List the providers the resolver supports. Use when the user asks things like \"Direct download link for https://drive.google.com/file/d/1oRRGuq_eDWEjauZZmowLu4m_57W3xqCc/view?usp=sharing please.\" or \"Which cloud drives and social platforms does the share link resolver support?\""
license: MIT
---

# Share Link Resolver jobs

Each section below walks through one job with the tools of the `sharelink` MCP server. The same recipes are MCP prompts (prompts/list) on `https://sharelink.openkrill.app/mcp`.
Connect the server at `https://sharelink.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Resolve a share link

Job: Resolve a share link, with the Share Link Resolver MCP server.

Use the `resolve_share_link` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Direct download link for https://drive.google.com/file/d/1oRRGuq_eDWEjauZZmowLu4m_57W3xqCc/view?usp=sharing please."

Steps:
1. Call `resolve_share_link` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `url`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"url":"https://drive.google.com/file/d/1oRRGuq_eDWEjauZZmowLu4m_57W3xqCc/view?usp=sharing"}`
4. For the request "Direct download link for https://drive.google.com/file/d/1oRRGuq_eDWEjauZZmowLu4m_57W3xqCc/view?usp=sharing please.", a correct answer looks like this: status ok, provider google_drive, one file epoch_485.pth with size and a drive.usercontent.google.com direct_url.
5. Follow the server's own rules:
   - Use resolve_share_link when the user pastes a Google Drive, Baidu Netdisk or social post link, or a short link from one of the covered platforms.
   - Pass the whole share message as url when it carries an extraction code.
   - For Google Drive, give the direct_url and the curl line; for a big file suggest the aria2c line.
   - For Baidu, list the files and say plainly that the download needs the user's own Baidu sign-in.
   - For a social link, give canonical_url as the clean link, and say what the item is when title is set.
   - If status is need_password, ask for the extraction code.
   - If status is private, say the owner must share it as Anyone with the link; never suggest a way around it.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `resolve_share_link`).

## List the providers the resolver supports

Job: List the providers the resolver supports, with the Share Link Resolver MCP server.

Use the `list_share_providers` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Which cloud drives and social platforms does the share link resolver support?"

Steps:
1. Call `list_share_providers` as a normal MCP tool call, with the request's values in the fields of its inputSchema.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{}`
4. For the request "Which cloud drives and social platforms does the share link resolver support?", a correct answer looks like this: Thirteen providers: two drives (google_drive with direct URLs, baidu with a file list) and 11 social platforms of kind social, each with its public interface, last verified date and the rules.
5. Follow the server's own rules:
   - Pass the whole share message as url when it carries an extraction code.
   - For Google Drive, give the direct_url and the curl line; for a big file suggest the aria2c line.
   - For Baidu, list the files and say plainly that the download needs the user's own Baidu sign-in.
   - For a social link, give canonical_url as the clean link, and say what the item is when title is set.
   - If status is need_password, ask for the extraction code.
   - If status is private, say the owner must share it as Anyone with the link; never suggest a way around it.
   - Call list_share_providers when the user asks which drives or platforms work.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `list_share_providers`).