Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok video

tiktok_video_get
Read-onlyIdempotent

Fetches a single TikTok video by URL and returns its details, with options to include the transcript or download media links for analysis or archiving.

Instructions

Get a single TikTok video by URL. Requires url. Author is identity-only (no follower counts) — use tiktok_profile_get for metrics. Credits: 1 (+downloadMedia add-on).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_video_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the video or photo post.
trimNoWhen true, returns a smaller response with fewer fields.
regionNoOptional ISO 3166-1 country code used to route the request when needed.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
downloadMediaNoWhen true, downloads the media and returns links to the files in `downloads` when available. Adds 10 credits when media is found (11 total including the base lookup); when no media is returned the base lookup credit still applies.
getTranscriptNoWhen true, includes the video transcript (WEBVTT) in `transcript` when one is available.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds cost transparency (1 credit, +downloadMedia add-on) and a genuine return-shape limitation ('Author is identity-only (no follower counts)'), which is behavioral context not present in annotations; the exact 11-credit math is duplicated from the schema's downloadMedia description.

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?

Three short sentences, front-loaded with the core action, then the requirement, then the sibling routing and cost. 'Requires `url`' is a minor redundancy since the schema already marks url required, but nothing else is wasted.

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 does some of that work by flagging that author data is identity-only and by disclosing credit pricing, so an agent knows roughly what comes back and what it costs. Remaining gaps — response shape, pagination/limits, and the interaction between the inline downloadMedia/getTranscript flags and the dedicated sibling tools — keep it below 5.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including url, trim, region, downloadMedia, getTranscript, context, llm_model and conversation_id is already well documented in the schema. The description only repeats that url is required and adds nothing about param interaction, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Get a single TikTok video') plus the identifier type (by URL), which is enough for an agent to distinguish it from profile-level tools. It names tiktok_profile_get as the metric-oriented alternative, though it does not clarify its boundary against the overlapping siblings tiktok_video_download_get and tiktok_video_transcript_get, which cover the downloadMedia/getTranscript flags this tool also exposes.

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 explicit routing: use this for a single video, use tiktok_profile_get when follower/metric data is needed. That is a real when-to-use/when-not pair, but it only covers one alternative; no guidance is given on when to prefer the dedicated download or transcript tools over the flags here.

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

Deploy Server

Other Tools