Skip to main content
Glama

TikTok videos of a profile

tiktok_videos
Read-onlyIdempotent

List a public TikTok profile's videos and photo posts, newest first, up to 15 per page, each with plays, likes, comments, shares, saves, caption, hashtags, mentions, date, duration and sound. First page: give username. Next pages: give only cursor until next_cursor is null.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoThe next_cursor of the previous answer, exactly as returned, for the next page. Leave it out for the first page; with it, nothing else is needed.
usernameNoA TikTok username (nasa), @nasa, or a profile link (https://www.tiktok.com/@nasa).
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 establish readOnly, idempotent, open-world, non-destructive behavior, and the description adds real context on top: a hard 15-per-page cap, newest-first ordering, the exact fields returned per item, and the loop termination condition. It stops short of covering failure modes such as private or nonexistent profiles, but the added behavioral detail is substantial.

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 dense sentences with zero filler: the first defines scope, ordering, page size, and payload; the second defines the paging protocol. The most important constraint for calling it correctly is front-loaded.

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 carries the burden of describing return fields and does so thoroughly, and it fully explains the pagination lifecycle. Minor gaps remain around behavior for private profiles and the media-URL flag, but nothing essential to a correct call is missing.

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 coverage is 100%, so username formats, cursor format, and include_media_urls are already fully documented in the schema. The description reinforces the cursor paging model and adds the 'until next_cursor is null' termination rule, but omits include_media_urls entirely, so it adds only marginal meaning beyond the structured fields.

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 ('List') plus resource ('a public TikTok profile's videos and photo posts'), and adds ordering and page size. It is clearly distinguishable from tiktok_video (single video) and tiktok_profile (profile metadata) because it names the collection being returned.

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 an explicit operating procedure: first page takes a username, subsequent pages take only the cursor, and iteration stops when next_cursor is null. It does not explicitly name a sibling to prefer for profile-level data, so differentiation from tiktok_profile is only implied.

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