Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_trending_effects

Retrieve TikTok trending effects and sticker discovery feeds with pagination, returning full video objects and cursors for trend research or content planning.

Instructions

Retrieve TikTok trending effects. Returns the effect/sticker discovery feed unmodified: aweme_list of full video objects, each additionally carrying stickers and sticker_detail, plus feed_session_id, cursor and has_more.

Input Schema

NameRequiredDescriptionDefault
countNoVideos per page (max 50)
cursorNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, but it usefully discloses that the feed is returned unmodified and lists the response fields including aweme_list, stickers, sticker_detail, feed_session_id, cursor and has_more. It does not discuss permissions, rate limits, or error behavior, so it is adequate but not rich.

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?

Two sentences with no waste: the purpose is front-loaded and the return details follow. Every clause contributes useful information about scope or payload shape.

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 low-complexity retrieval tool with complete schema descriptions and no output schema, the description sufficiently outlines the return structure and pagination fields. It leaves out usage guidance and explicit pagination instructions, which prevents a perfect score.

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 count and cursor are already documented in the input schema. The description mentions cursor only in the return payload and adds no input-parameter semantics beyond the schema, so baseline 3 is appropriate.

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 and resource: retrieving TikTok trending effects, and clarifies it is the effect/sticker discovery feed rather than generic videos. It does not explicitly differentiate from the sibling tiktok_mobile_live_effects, so it falls 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 Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and no comparison to siblings such as tiktok_mobile_live_effects or tiktok_mobile_feed. Usage is only implied by the word 'trending'.

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