tiktok_collection_videos_listList videos in a public TikTok collection by URL. Returns a list (use cursor when paginated).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public TikTok collection URL. | |
| cursor | No | Pagination cursor returned by a previous response. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety expectations. The description adds that the tool returns a list and mentions cursor-based pagination, which is useful behavioral context. It does not contradict annotations and provides a basic sense of the output structure and handling of large result sets, though it omits other potential behaviors like rate limits or error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is exceptionally concise, consisting of two short sentences that convey the core purpose and pagination behavior in a front-loaded manner. There is no unnecessary filler or redundancy, making it easy for an agent to quickly parse the essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list-by-URL tool with fully documented parameters and no output schema, the description adequately covers the primary behavior (listing videos) and pagination. However, it does not describe the format of each returned video object or any potential edge cases (e.g., invalid URL, empty collection). Given the tool's simplicity and the presence of annotations, this is acceptable but not fully comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides descriptions for both parameters ('url' and 'cursor') with 100% coverage. The description essentially reiterates these concepts ('by URL' and 'use cursor when paginated') without adding any new semantic detail or constraints. Since the schema already documents the parameters fully, the description adds minimal value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists videos from a public TikTok collection identified by URL. It uses a specific verb ('List') and resource ('videos in a public TikTok collection'), and the mention of 'by URL' distinguishes it from other TikTok listing tools that use different identifiers. Though it doesn't explicitly differentiate from sibling tools like tiktok_profile_videos_list, the term 'collection' provides sufficient distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or comparisons to sibling tools that list videos (e.g., profile videos, search videos). The only hint is the resource type ('collection'), which implies usage when a collection URL is available, but this is not explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.
All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).
The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.
The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.