Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_place_videos

Fetch paginated TikTok videos posted at a specific place using its poi_id, returning full video objects and a reusable cursor for the next page.

Instructions

Videos posted at one place (paged). Returns one page of the videos posted at a place, keyed by the poi_id that the place search endpoint returns. The upstream is /tiktok/poi/video/list/v1: aweme_list holds the app's full video objects (id, description, author, statistics, media URLs, music, anchors, ...) and item_count is this page's size. Page with cursor: the returned cursor is a reusable next-page token (measured page 1 cursor: 20 with has_more: 1, page 2 cursor: 40), never with arithmetic on count. count is a page-size hint, not a strict size: 1/2/5 returned exactly that many items on the first page, a later page returned 8 for count=5, and 10/20/50 were all server-capped at 17. Measured 2026-10-21: 11 videos (940-944 KB) on one place, 17 videos (1.4 MB) on another. The route exposes no sort control: sort_type and order were measured and did not change the page or its order. The upstream throttles bursts, so paced clients are expected.

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": {
      "poi_id": "<poi_id>"
    },
    "name": "tiktok_mobile_place_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoPage-size hint: 1-50 measured, server caps larger pages (default is the app default)
cursorNoNext-page token from the previous response (0 = first page)
poi_idYesPlace id from the place search endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: it names the upstream route, the response shape (`aweme_list`, `item_count`), the pagination token semantics, the soft page-size cap (~17), and burst throttling. It does not discuss auth requirements or error/failure behavior, which keeps it from 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?

Purpose is front-loaded in the first clause, and the remaining sentences each carry operational detail. The measured payload sizes (940-944 KB, 1.4 MB) are borderline trivia but useful for sizing expectations; otherwise there is no filler.

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

Completeness5/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 takes on return-value disclosure itself (lists the fields inside `aweme_list`, explains `item_count`), and it also covers pagination, the absence of sort controls, and rate-limit behavior. An agent has everything needed to call and page it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description adds real meaning: `cursor` is a reusable next-page token with observed 20→40 progression, `count` is only a hint (1/2/5 honored, 10/20/50 capped at 17, one page returned 8 for count=5), and `poi_id` is sourced from the place search tool. This is materially beyond the schema text.

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 ('Videos posted at one place'), explicitly notes it is paged, and anchors the resource key to `poi_id` from the place search endpoint. That cleanly separates it from `tiktok_mobile_place_photos` and `tiktok_mobile_place_detail`, though no sibling is named directly.

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

Usage Guidelines4/5

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

Gives the prerequisite for `poi_id` (comes from the place search endpoint), tells the caller how to page (use the returned `cursor`, never arithmetic on `count`), and warns that sort is not controllable and that the upstream throttles bursts. It lacks an explicit 'use X instead when...' routing statement, so it stops short of a 5.

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