Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_challenge_list

Fetch TikTok hashtag posts by hashtag ID, returning video items with pagination cursor to retrieve additional pages.

Instructions

Retrieve TikTok hashtag posts. Lists the videos posted under a TikTok hashtag, identified by the hashtag id from the hashtag detail endpoint. cursor defaults to 0. The response has itemList, hasMore and a cursor; pass that cursor back to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
idYesHashtag id returned by the hashtag detail endpoint
cursorNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 well: it discloses that `cursor` defaults to 0, reveals the response shape (`itemList`, `hasMore`, `cursor`), and explains the pagination loop. Auth, rate limits, and ordering (e.g., recency) remain unstated, but the operational behavior is substantially covered.

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

Conciseness5/5

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

Three front-loaded sentences with zero filler: purpose first, then parameter sourcing and default, then pagination mechanics. Every sentence earns its place.

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 two-parameter read tool with no output schema, the description is nearly self-sufficient: it covers input sourcing, the default, and the full response/pagination contract. Only peripheral details (auth, rate limits, sort order) are missing.

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 baseline is 3, but the description adds genuine meaning beyond the schema: it says `id` originates from the hashtag detail endpoint and that `cursor` defaults to 0, plus how the returned cursor is reused. These are concrete semantic additions, not restatements.

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 ("Retrieve TikTok hashtag posts... Lists the videos posted under a TikTok hashtag"), which distinguishes it from a hashtag-detail tool by pointing to the `id` source as "the hashtag detail endpoint." It is clear and slightly differentiating, though it never names the sibling (tiktok_challenge / tiktok_mobile_hashtag_posts) directly.

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?

Usage is implied: it tells you where the `id` comes from and how to page, so an agent can infer when this applies. However, there are no explicit when-to-use rules or named alternatives despite several resembling siblings (tiktok_challenge, tiktok_mobile_hashtag_posts, tiktok_search_hashtag).

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