Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_feed

Retrieve one page of TikTok’s mobile For You feed using cursor and count controls, including verified play, like, comment, share, and collect statistics for each video.

Instructions

Retrieve the TikTok mobile For You feed. Returns one page of videos from TikTok's mobile For You feed. Each item carries aweme_id, create_time, author_id, share_url and the verified statistics block (play_count, digg_count, comment_count, share_count, collect_count, download_count, forward_count, lose_count, lose_comment_count, whatsapp_share_count, repost_count). A zero count uses the app's default page size; count is capped at 50.

Input Schema

NameRequiredDescriptionDefault
countNoVideos to request (0 = app default, max 50)
cursorNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A3.7/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 a good job disclosing that it returns one page, lists the item fields, and explains count default/cap behavior. It omits auth, rate-limit, and personalization details, but the core retrieval behavior is transparent.

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 purpose is front-loaded and the field list earns its place because there is no output schema. The first two sentences repeat the same feed concept, but overall the description is structured and reasonably concise.

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 feed tool with no output schema and no annotations, the description is fairly complete: it explains the feed, page behavior, return fields, and count limits. Cursor continuation semantics are left to the schema, which is a minor gap.

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 count and cursor. The description repeats count's 0-default and 50-cap behavior but adds no meaningful cursor semantics beyond what the schema provides; 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 states a specific verb and resource: retrieving the TikTok mobile For You feed. It is clear enough to distinguish from most siblings by naming the exact feed type, though it does not explicitly contrast with tiktok_mobile_search, tiktok_explore, or feed-post tools.

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 by the purpose: call this when you want the mobile For You feed. However, there is no explicit when-to-use guidance, no exclusions, and no routing advice against the many TikTok siblings.

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