Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_place_photos

Retrieve a place's TikTok photo album with per-photo attribution by passing the poi_id returned from place search. Use it to access album categories, photo counts, titles, and credited image URLs.

Instructions

Place photo album with per-photo attribution. Returns one place's photo album, keyed by the poi_id that the place search endpoint returns. The upstream is /tiktok/poi/picture_album/v1: categories holds each album tab (name, pic_tab_typecode, pictures of bare image URL lists and pictures_v2, the same photos with author attribution, pic_id, source and origin/compressed URL info), photo_count sums the categories' pictures, and title is the app's own header. Measured 2026-10-21: one place answered 5,368 B, title "Gallery (3)", 1 category with 3 photos whose pictures_v2 entries name the Google-places contributor; another answered 24,196 B with more photos. The album is one-shot: count and pic_tab_typecode were measured and did not change the page. A nonexistent id answers 500 (the upstream answers status 4 "Server is currently unavailable" on this route, unlike the poi-not-exist code the other place routes use).

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

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.5/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 disclosure burden and does so: it describes the exact response shape (`categories` with `pictures`/`pictures_v2`, `photo_count`, `title`), the attribution semantics, the one-shot nature (no pagination, `count`/`pic_tab_typecode` don't change the page), and concrete error behavior — nonexistent id returns 500 with upstream status 4 'Server is currently unavailable', explicitly contrasted with the poi-not-exist code on other routes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and key are front-loaded, but the bulk is one dense run-on sentence covering response shape, and it includes low-value measurement trivia (5,368 B, 24,196 B, date-stamped observation) that an agent does not need to call the tool. The error and one-shot notes do earn their place; the byte counts do not.

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, so the description must explain returns — and it does so in detail, down to the difference between `pictures` (bare URLs) and `pictures_v2` (with `author`, `pic_id`, `source`, origin/compressed URLs). Failure modes are also covered, leaving nothing an agent needs before calling it.

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 schema already documents `poi_id`; the description adds real value by specifying its provenance (place search endpoint) and by warning that other upstream parameters (`count`, `pic_tab_typecode`) are measured as inert, which preempts futile experimentation.

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 and resource — 'Returns one place's photo album' — and immediately distinguishes it from the place search route by naming the key it consumes (`poi_id` from the place search endpoint). An agent can tell it apart from sibling place tools (place_detail, place_videos, place_info) without opening any 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?

It states the prerequisite clearly (the id must come from the place search endpoint) and implies the usage context (fetching a place's photo album). It does not name alternative tools or say when not to use this one, so it falls short of a 5, but the prerequisite alone is enough for correct routing.

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