Skip to main content
Glama

TikTok video or photo post

tiktok_video
Read-onlyIdempotent

Get one public TikTok video or photo post: caption, plays, likes, comments, shares, saves, date, duration, hashtags, mentions, sound, location, categories, the ad flag, and its author with their counts. For its comments, call tiktok_comments.

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": "tiktok_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA TikTok video or photo link (https://www.tiktok.com/@nasa/video/7695060950394703118), a short link from the app (vm.tiktok.com/…, vt.tiktok.com/…, tiktok.com/t/…) or the video id.
include_media_urlsNoAlso return picture, video and sound file links (long links that expire after a while). Leave it off unless you need the files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, open-world, non-destructive), so the description's job is to add context - and it does by scoping the tool to public posts and itemizing the returned data, which matters because there is no output schema. It stays silent on failure modes such as private, deleted, or region-blocked posts, but the added disclosure is well beyond what the annotations convey.

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

Conciseness5/5

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

Two sentences, both earning their place: the first front-loads scope and the return payload, the second handles the routing case. No filler or restatement of the tool name.

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 field enumeration is doing essential work, and the public-only qualifier plus the comments hand-off round it out. What remains thin is behavior on unavailable or private posts, which an agent would want to know before calling.

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%; both url (accepted link formats, id) and include_media_urls (expiring links) are fully documented in the schema itself. The description adds no syntax or format meaning beyond that, so the baseline of 3 applies.

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 one public TikTok video or photo post') and enumerates the returned payload - caption, plays, likes, author counts, ad flag - so the agent knows exactly what comes back. 'One' distinguishes it from the plural tiktok_videos listing, and the trailing sentence separates it from tiktok_comments.

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?

Explicitly routes the adjacent use case: 'For its comments, call tiktok_comments.' That is a concrete alternative with a condition attached. It does not, however, say when to prefer this over tiktok_profile or tiktok_videos, so the guidance is clear but not exhaustive.

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