Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_mv_videos

Fetches one page of a TikTok MV channel feed by numeric channel index, with cursor-based pagination, returning full music-video entries for browsing or data collection.

Instructions

MV channel feed: the app's music-video tab, paged. Returns one page of an MV channel feed, the app's music-video ("MV") tab. The upstream is /aweme/v1/mv/aweme/; mv_id is a small numeric CHANNEL index, NOT a video id — measured ids 0-10 each returned a 15-video page of full aweme objects (1.05-1.24 MB), while 100 returned a valid empty page and a real aweme id returned an empty list. The server's page size is 15 and count was measured IGNORED (count=5 and count=10 both returned 15 items), so count is not exposed; page with cursor. The returned cursor is a reusable next-page token (measured page 1 cursor: 18, has_more: 1; cursor=18 returned a fresh page with cursor: 38, has_more: 1). The envelope's top_awemes (pinned entries), original_aweme_id, page_extra and extra/log_pb are kept as measured. Measured 2026-10-22, A missing or non-numeric mv_id is a 400; an unknown numeric channel is a valid empty page.

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": {
      "mv_id": "<mv_id>"
    },
    "name": "tiktok_mobile_mv_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
mv_idYesMV channel index (small integer; measured 0-10 populated, 100 empty)
cursorNoNext-page token from the previous response (0 = first page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: page size is fixed at 15, `count` is measured as ignored and thus not exposed, cursor values are reusable next-page tokens, responses are large (1.05-1.24 MB), and error behavior is documented.

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?

The description is front-loaded and information-dense, but it repeats the same MV-feed framing twice at the start ('MV channel feed' and then 'Returns one page of an MV channel feed'). The remaining measurement details are useful, so the minor redundancy only costs one point.

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?

No output schema exists, so the description appropriately covers response size, page size, cursor chaining, error cases, and envelope fields such as `top_awemes`. It is nearly complete, though it does not explain how an agent should discover valid `mv_id` channel values beyond the measured 0-10 range.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: `mv_id` is a small numeric channel index rather than a video id, ids 0-10 are populated, 100 and real aweme ids return empty, and `cursor` is a reusable next-page token. The added empirical semantics justify a 4.

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: returns one page of an MV channel feed, the app's music-video tab. The purpose is clear, but it does not explicitly differentiate itself from nearby TikTok mobile feed or music-post 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 explains pagination via `cursor` and the numeric-channel semantics of `mv_id`, including that a missing/non-numeric id is a 400. It gives no explicit guidance on when to choose this tool versus sibling tools such as `tiktok_mobile_music_posts` or `tiktok_mobile_feed`.

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