Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List TikTok collection videos

tiktok_collection_videos_list
Read-onlyIdempotent

Retrieve videos from a public TikTok collection by URL and paginate results with a cursor to collect all videos in manageable pages.

Instructions

List videos in a public TikTok collection by URL. Requires url. Returns a list (use cursor when paginated).

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_collection_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public TikTok collection URL.
cursorNoPagination cursor returned by a previous response.
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.
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds pagination behavior via the cursor, which is genuine value, but says nothing about rate limits, error behavior on private/invalid collections, or result shape.

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 short sentences, requirement and pagination note front-loaded, with no redundant or filler wording.

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 a simple read-only listing tool with rich annotations and full schema coverage, the definition is adequate but thin: it never mentions that the collection must be public beyond the schema, nor what happens with an expired cursor. It stops at minimum viable rather than anticipating an agent's failure modes.

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 description coverage is 100%, so the baseline is 3; the description goes slightly beyond by noting the cursor is for paginated continuation, reinforcing the schema's wording. It adds little else, since `url`, `context`, `llm_model` and `conversation_id` are fully documented in the schema.

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 ("List videos in a public TikTok collection") plus the input form ("by URL"), which implicitly separates it from profile, search and music video siblings. It does not explicitly name an alternative, so it falls short of a 5.

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 phrase "by URL" and "Requires `url`" imply this is the collection-scoped lister, and "use cursor when paginated" gives a light runtime hint. There is no explicit statement of when to choose this over tiktok_profile_videos_list or tiktok_search_videos_list, nor any prerequisite guidance.

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