Skip to main content
Glama

social-media-video-downloader

Get Tweet Details

get_twitter_v3_post_details

Supply tweetId or url. tweetId takes precedence. Returns full text, author and engagement metadata, and ordered photo/video/GIF attachments. Each video also has a renderableAudios item whose renderConfig produces an M4A of its audio: the HLS audio rendition when the playlist has one, otherwise the audio of the medium-quality MP4. Text-only tweets succeed with contents=[] and metadata.post.isTextOnly=true. Deleted or private tweets return an error. The former prototype postId parameter is replaced by tweetId. Group: Twitter-Tweet. Billing per call: 1 Credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_twitter_v3_post_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAn http(s) X/Twitter status URL or t.co short link. Photo/video suffixes and query strings are supported. Required unless tweetId is supplied.https://x.com/jack/status/20
langNoPreferred page language, passed in the page URL, Accept-Language header and media request headers. Defaults to en. Does not translate tweet text.
tweetIdNoNumeric tweet ID. Required unless url is supplied.2116307188155400526

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the text-only success path (contents=[] with metadata.post.isTextOnly=true), the failure mode for deleted/private tweets, per-call billing of 1 credit, and the deprecation of the old postId parameter. Auth requirements and rate limits are the notable omissions.

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?

Front-loaded with the input choice, then returns, then edge cases, then billing — a sensible order with no filler sentences. The renderableAudios/renderConfig/M4A passage is dense and niche, but it is the kind of detail an agent needs to know exists in the response.

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

Completeness4/5

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

With no output schema, the description correctly compensates by sketching the response shape (text, author, engagement, ordered media attachments) and the two important edge cases. It stops short of describing the error payload format or auth/rate-limit expectations, which keeps it just under full completeness.

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 genuine meaning the schema does not: the precedence rule when both tweetId and url are supplied, and the migration note that postId is replaced by tweetId. This resolves the exact ambiguity the schema leaves open.

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?

Opens with the required input and then states precisely what is returned: full text, author and engagement metadata, and ordered photo/video/GIF attachments. The platform-specific name plus the explicit return payload make it trivially distinguishable from the Facebook/Instagram/TikTok post-details siblings.

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?

Gives clear calling context: supply tweetId or url, with tweetId taking precedence, and warns that deleted or private tweets return an error. It does not name alternatives, but no sibling covers single-tweet retrieval for X/Twitter, so there is little to route away to.

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