Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_search_place

Search TikTok places by keyword to map a location or category and inspect each result's video count, rating, coordinates, and details.

Instructions

Search TikTok places. Returns TikTok's place (POI) search results for a keyword, unmodified: each row carries poi_name, poi_id, poi_type, video_count, poi_rating, poi_distance, poi_location, lat/lng, img_url, opening_time, price_level and parent_poi. Useful for mapping a location or category to the places TikTok knows about, and for seeing how many videos each place carries. keyword is required. The page holds up to 30 rows (count 1-30 measured; a larger count makes the upstream answer an empty page, so the service rejects it) and the route is first-page-only — the returned cursor is not a reusable page token.

Input Schema

NameRequiredDescriptionDefault
countNoRows to return, 1-30 measured (a larger count yields an empty upstream page and is rejected)
keywordYesPlace name or category to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/5.0
Behavior4/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 well: it discloses that results are returned unmodified, that count above 30 yields an empty upstream page and is rejected, and that the route is first-page-only and the cursor is not a reusable token. Missing only peripheral behavior such as whether results are localized or regional, which is a modest gap for a read-only search endpoint.

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 and return fields, then usage, then constraints, in a single readable passage. The 1-30 count rule is stated twice in the description and again in the schema, a minor redundancy, but no sentence is padding.

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?

There is no output schema, and the description compensates by naming every row field, plus documenting page size ceiling and the dead-end cursor. An agent can call this correctly and interpret the response without further information.

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 the schema already documents both parameters, including the 1-30 count limit. The description only restates that keyword is required and repeats the count cap, adding essentially nothing new about parameter meaning or accepted keyword forms.

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 ('Search TikTok places') and enumerates the returned POI fields, which pins down what the tool actually produces. It does not explicitly distinguish itself from sibling TikTok place tools such as tiktok_mobile_place_detail or tiktok_mobile_search_pre_info, so the sibling differentiation that would earn a 5 is absent.

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 concrete usage context: mapping a location or category to places TikTok knows about, and comparing video counts per place. It also discloses the first-page-only constraint that shapes how you should use it. It stops short of naming alternatives (e.g. use place_detail to drill into one POI), so no explicit when-not guidance.

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