Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_music_collections

Fetch TikTok mobile sound collections as JSON, returning each collection with its music list, cursor, and has_more flag for first-page access.

Instructions

Retrieve TikTok music collections. Returns the mobile app's sound-collection feed unmodified: mcf_list, where each entry is {collection, music_list} (the measured default page holds 8 entries), plus cursor and has_more. This route is first-page only: the returned cursor is not a reusable page token, so callers should not page with it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoCollections to request (0 = app default, max 50)
cursorNoAccepted for shape compatibility only; not a verified page token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does so well: it discloses the response envelope (mcf_list, cursor, has_more), the measured page size of 8, and the critical non-reusable-cursor limitation. Auth requirements and rate limits remain unstated, keeping it short of a 5.

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

Conciseness4/5

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

Front-loaded with purpose, then return shape, then the pagination caveat. Every sentence earns its place; the only minor redundancy is restating the non-pageable cursor that the schema also flags.

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 and no annotations, the description supplies the return structure, payload field names, page size, and a pagination warning, which is enough for an agent to call it correctly. It stops short only on auth/rate-limit context.

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 both parameters are already documented. The prose adds only marginal value, clarifying that count=0 yields the app default of 8 entries and reinforcing that cursor is shape-compatibility-only, which merely mirrors 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?

Specific verb 'Retrieve' plus resource 'TikTok music collections' scoped as 'the mobile app's sound-collection feed unmodified'. This distinguishes it from adjacent siblings like music_trending or music_posts, though it never names an alternative explicitly.

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?

Gives one useful operational exclusion ('first-page only... should not page with it'), but offers no guidance on when to reach for this tool versus the other tiktok_mobile_music_* siblings. Usage is implied by the scope rather than stated.

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