Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List TikTok profile videos

tiktok_profile_videos_list
Idempotent

List videos from a TikTok profile by handle, with pagination, sorting, and optional media hosting for direct delivery URLs.

Instructions

List videos from a TikTok profile by handle. Requires handle. Credits: 1 base; hostMedia=true adds +2 per hosted asset (up to 24 / 49 max). Failed assets are not surcharged.

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_profile_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoOptional flag for a smaller response with fewer fields.
cursorNoPagination cursor returned by a previous response.
handleYesRequired. TikTok handle whose videos should be listed.
regionNoOptional ISO 3166-1 country code for the request.
sortByNoOptional sort order for the returned TikTok videos.
userIdNoOptional TikTok user id to speed up the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
hostMediaNoWhen true, hosts source media for 90 days and returns delivery URLs in each video's `hostedMedia`.
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.
includePinnedNoWhether to include videos pinned to the top of the profile. Default: `true`. Set `false` to leave pinned videos out; pages can then come back shorter or empty, so keep following `hasMore` and `cursor`. Send the same value on every page.
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 disclose open-world, non-destructive, idempotent behavior and readOnlyHint=false. The description adds meaningful behavioral context beyond that: 1 base credit, +2 per hosted asset when hostMedia=true, caps of 24/49, and no surcharge for failed assets. It does not explain pagination or response format, but the cost and side-effect transparency is valuable.

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?

Three compact sentences, front-loaded with purpose and requirement, then the credit rules. No redundant restatement of schema details.

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

Completeness3/5

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

For an 11-parameter, open-world list tool with no output schema, the definition covers purpose, required handle, and cost but does not describe the response shape, pagination behavior, or how includePinned and cursor interact across pages. The rich schema fills most gaps, but the description itself is not fully complete.

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 the schema already explains all 11 parameters, including cursor, sortBy, includePinned, and hostMedia. The description reinforces the required handle and adds credit-cost meaning for hostMedia, but leaves the other parameters to the schema; baseline 3 is appropriate.

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), resource (videos), and scoping key (TikTok profile by handle). This clearly separates it from search-, music-, or collection-based video list siblings.

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

Usage Guidelines3/5

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

The description establishes the use case as listing videos for a profile handle and notes that handle is required. However, it gives no explicit when-to-use/when-not guidance or named alternatives such as search_videos_list, so usage is implied rather than directed.

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