Skip to main content
Glama

Download a social media post

download_social

Get the video and photos of a social media post (X/Twitter, Douyin, Xiaohongshu/RedNote, Instagram) as direct download URLs, in one call. Use it whenever the user shares such a link or asks about a post's video or pictures: to save, watch, transcribe, describe or analyze them. The files are small (short videos, photos): fetch the URLs and work on them directly (at most 3 at once; resume a cut download with an HTTP Range request). A post with several photos or videos returns them all (up to 20, items) and counts as one free download; social posts have their own free allowance (20 a day).

    Files not ready within `wait_seconds` have status "running" and a `job_id`: call `get_job`, then
    `get_download_link`.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "download_social"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLink to a post on X (Twitter), Douyin, Xiaohongshu (RedNote) or Instagram, as the user gave it
tierNo"free" (own daily allowance for social posts) or "fast" (uses traffic balance)free
wait_secondsNoHow long to wait for the files to be ready

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing file size expectations, a concurrency cap ('at most 3 at once'), HTTP Range resumption for cut downloads, a 20-item cap for multi-media posts, the free-tier accounting rule (one post = one download, 20/day), and the wait_seconds timeout path (status 'running' plus job_id, then get_job and get_download_link). Nothing here contradicts the declared readOnlyHint=false and openWorldHint=true profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and trigger are front-loaded in the first two sentences, and the follow-up sentences carry operational detail rather than filler. It is dense and slightly long, with a couple of parenthetical asides, but nearly every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be documented, yet the description still covers the two things an agent must act on: multi-item results ('up to 20, items') and the async continuation path via job_id. Combined with the quota and concurrency notes, an agent has everything needed to call this correctly on the first try.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains what wait_seconds governs (files not ready become 'running' with a job_id) and what the tier choice costs ('free' uses the social daily allowance, implied 'fast' consumes traffic balance). The URL parameter itself is only restated, not enriched.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the video and photos of a social media post') and scopes it to four named platforms, returning 'direct download URLs, in one call'. This lets an agent distinguish it from the generic sibling 'download' and from link-handling tools like check_link without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger conditions are given: 'Use it whenever the user shares such a link or asks about a post's video or pictures', with concrete downstream purposes (save, watch, transcribe, describe, analyze). It does not name a when-not case or point to a specific alternative for non-social links, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources