Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_challenge

Fetch TikTok hashtag details by name, including metadata, cover images, and share title/description. Use the returned hashtag ID to feed challenge lists.

Instructions

Retrieve TikTok hashtag details. Returns the details of a TikTok hashtag page by name, for example christmas. The response carries challengeInfo with the hashtag's metadata, such as cover images, and shareMeta with the share title and description. The hashtag id found here feeds tiktok-challenge-list.

Input Schema

NameRequiredDescriptionDefault
nameYesHashtag name (e.g., 'christmas')

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?

No annotations are provided, so the description carries the full burden. It discloses the return shape (`challengeInfo` with metadata/cover images, `shareMeta` with share title/description) and implies a read-only retrieval, but says nothing about auth, rate limits, pagination, or behavior when the hashtag does not exist.

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-loads the core purpose in the first sentence, then adds return-shape and chaining detail. Three sentences are mostly efficient, though the return-shape sentence is somewhat detailed relative to a one-parameter read tool.

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?

With no output schema, the description usefully explains what the response contains, and the chaining note orients the agent to the next tool. It is close to complete for a simple read tool, missing only edge-case behavior (nonexistent hashtag) and auth expectations.

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 coverage is 100% and the single `name` parameter is already documented with the same `christmas` example. The description restates the parameter meaning ('by `name`, for example `christmas`') without adding format or constraint detail beyond the schema, so the baseline 3 applies.

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 details') and grounds it with a concrete example (`christmas`). It also names a relationship to `tiktok-challenge-list`, giving some sibling differentiation, though it does not distinguish from other hashtag-adjacent siblings like `tiktok_mobile_hashtag` or `tiktok_search_hashtag`.

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?

There is no explicit when-to-use/when-not guidance or named alternative. Usage is only implied through the note that the hashtag id 'feeds tiktok-challenge-list', which hints at a workflow but does not tell the agent when to pick this tool over the other hashtag tools.

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