Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_place_detail

Fetch a TikTok place-detail page by poi_id from place search to return address, category, hours, rating, photos, a video strip, posts, review previews, and AI summary for a location.

Instructions

Place (POI) detail from the mobile app's Places surface. Returns one place detail page, keyed by the poi_id that the place search endpoint returns. The upstream is TikTok's server-driven UI (/tiktok/poi/slash/v1) frame stream, assembled here into the component map of the place-detail screen: food_head_info (place name, formatted address, category, phone, coordinates, opening hours, rating/score with mention count, price range, tags and photo album), poi_top_videos (top videos strip), poi_limited_post (posts about the place: full video items plus aweme_cursor/has_more_aweme), poi_review (review preview with has_more) and ai_summary when the place has one. nodes is opaque and complete, frames keeps the raw ordered frames, and the typed counters (top_video_count, post_count, post_cursor, has_more_posts, review_count, has_more_reviews) are convenience projections. The measured page-size controls are forwarded with the app's defaults but the server applies its own bounds. The route is not signature-gated, so it does not need the device-backed signer.

Input Schema

NameRequiredDescriptionDefault
poi_idYesPlace id from the place search endpoint
enter_fromNoForwarded analytics origin (default search_places)
merged_countNoPosts page size forwarded upstream (default 9, bounded at 50)
review_countNoReview preview size forwarded upstream (default 20, bounded at 50)
video_cursorNoTop-videos cursor forwarded upstream (default 0)
review_cursorNoReview cursor forwarded upstream (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/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 unusually well: it explains the upstream is a server-driven UI frame stream assembled into a component map, that nodes is opaque yet complete and frames retains raw ordering, that counters are convenience projections, that the server applies its own bounds to page sizes, and that the route needs no device-backed signer. It only omits an explicit read-only/side-effect statement, though 'detail' implies it.

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 and key are front-loaded in the first sentence before the dense component-map enumeration, and each section (input source, return assembly, counters, sizing, auth) earns its place. It is long but the density is justified by the complex UI-frame return structure.

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, but the description compensates by describing the component map, opaque nodes, raw frames, and typed counters in detail, plus the pagination-related counters and auth caveat. For a 6-param detail tool this is nearly complete; the only gap is explicit sibling routing among the other place endpoints.

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 coverage is 100%, so the schema already documents all six params including defaults and bounds. The description's added value is the note that measured page-size controls are forwarded with app defaults but bounded server-side, which is marginal beyond what the schema states. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Place (POI) detail ... Returns one place detail page') and pins down the key ('poi_id that the place search endpoint returns'), which disambiguates it from siblings like tiktok_mobile_search_place or tiktok_mobile_place_photos. An agent knows exactly what it fetches without opening the schema.

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 clear context for use: you supply a poi_id sourced from the place search endpoint, so the retrieval chain is explicit. It does not name the sibling detail surfaces (place_info, place_photos, place_videos) or state when to prefer this over them, so it stops short of explicit alternatives/exclusions.

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