Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_explore

Retrieve the TikTok explore feed for a category by its category type id to surface videos; use itemList, hasMore, and cursor to page through results.

Instructions

Retrieve the TikTok explore feed for a category. Returns the TikTok explore feed for a category, given its category type id from the category endpoint. The response has itemList with the videos, hasMore and a cursor. A feed that comes back empty is reported as an upstream error, not as an empty list.

Input Schema

NameRequiredDescriptionDefault
idYesCategory type id returned by the category endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses genuinely useful behavior: the return shape (itemList, hasMore, cursor) and the non-obvious rule that an empty feed surfaces as an upstream error rather than an empty list. It stops short of explaining pagination mechanics or auth/rate-limit behavior.

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?

The description is compact and front-loads the core purpose, with the response shape and error behavior following logically. The first two sentences overlap ('Retrieve...' then 'Returns...') introducing mild redundancy.

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?

For a single-parameter read tool with no output schema, the description covers purpose, the input source, the response fields, and the notable empty-feed error semantics. Pagination usage of the cursor is the main omission.

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 the single `id` parameter, establishing a baseline of 3. The description restates that the id comes from the category endpoint without adding format or constraint detail beyond the schema.

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?

The description names a specific verb ('Retrieve') and resource ('TikTok explore feed for a category'), and ties the input to the category endpoint, so an agent can distinguish it from tiktok_category. It does not explicitly differentiate from other feed siblings like tiktok_mobile_feed, keeping it short of a 5.

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

Usage Guidelines3/5

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

It states the prerequisite that the `id` must come from the category endpoint, implying a two-step flow. There is no explicit when-not-to-use guidance or comparison to alternative feed tools, so usage is only implied.

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