Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_place_info

Fetch a compact TikTok place (POI) record by poi_id to get address, coordinates, rating, hours, and counters without loading the full detail page.

Instructions

Compact place (POI) record: address, coordinates, rating, hours, counters. Returns one place's compact record, keyed by the poi_id that the place search endpoint returns. The upstream is TikTok's POI read (/tiktok/poi/get/v1), the record behind a place card: name, address, category, average_price, latitude/longitude, city_code/region_code, review_score with review_count/no_rating, video_count, favorite_count, opening_hours/opening_status, cover, share_url/share_desc and parent_poi, plus the upstream POI object unmodified in place so a richer field is never lost. This is the cheap lookup to use instead of the ~1 MB slash detail page when only the place record is needed. A nonexistent id answers 400 (the upstream business status 3009009 "poi not exist" is a caller error, not an outage). Measured 2026-10-21: 4,594 B for a coffee shop (score 4.7 / 2 reviews, price "$", hours "8:00 AM – 5:00 PM", 11 videos), 4,623 B for a second location (score 4.8 / 13 reviews).

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
poi_idYesPlace id from the place search endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.8/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 richly: it names the upstream POI endpoint, enumerates the returned fields (including the preserved raw `place` object), discloses the exact failure mode (400 / status 3009009 'poi not exist', flagged as a caller error not an outage), and gives measured response sizes for calibration.

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 the core purpose and reasonably efficient, but the exhaustively long field enumeration and byte-size measurements make it denser than strictly necessary. Every part is informative, though the field list pushes toward verbosity.

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 must describe return contents — and it fully enumerates the fields plus the preserved raw object. Error behavior, data source, and payload sizing are all covered, making it self-sufficient for correct invocation.

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?

Only one parameter with 100% schema coverage, so the schema already defines poi_id. The description adds value by stating where the id comes from and what happens with an invalid one (400), reinforcing the parameter's contract beyond the bare schema text.

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?

The description opens with a specific verb+resource ('Returns one place's compact record') and explicitly differentiates from the sibling place_detail ('the cheap lookup to use instead of the ~1 MB slash detail page'). An agent can distinguish it from tiktok_mobile_place_detail, place_photos, and place_videos without opening a schema.

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

Usage Guidelines5/5

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

It names the alternative (the ~1 MB detail page) and states the exact condition selecting this tool ('when only the place record is needed'). It also specifies the required provenance of the id (from the place search endpoint), leaving nothing to inference.

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