Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_mobile_user_recommendations

Discover recommended TikTok creators from the mobile Following page. Returns full profiles and recent videos to help identify new accounts to follow.

Instructions

Recommended creators on the mobile app's Following page. Returns the app's suggested creators for the Following page unmodified: user_list entries are {user, aweme_list} where user is the full creator projection (uid, sec_uid, nickname, signature, avatars, follower/following counts, verification and privacy flags) and aweme_list holds up to three recent videos, so this is a creator-discovery surface rather than a bare id list. The route has no paging fields and returns one page of 13-17 creators (fresh recommendations differ per call). count is accepted for parity but the gateway was measured to ignore it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_mobile_user_recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoRequested page size; forwarded when set, but the gateway was measured to ignore it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it states the return structure (`user_list` entries with `{user, aweme_list}`), explains that creator projections are full and include up to three recent videos, notes there are no paging fields, gives a typical page size of 13-17, and warns that fresh recommendations differ per call and that `count` is ignored by the gateway. This is rich, concrete behavioral context.

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?

The description is front-loaded with the core purpose and then adds only high-value details about return shape, page-size variability, and the ignored `count` parameter. Every sentence contributes useful information, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description explains the returned `user_list` structure, the fields in each creator projection, the presence of up to three videos per creator, the lack of paging, and the variability of results. For a one-parameter tool with no annotations, it gives the agent everything needed to invoke the tool correctly and understand its output.

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% and the only parameter, `count`, is already documented with its caveat in the schema. The description repeats the same caveat ('accepted for parity but the gateway was measured to ignore it') but adds no new syntax, format, or alternative meaning beyond what the schema provides. A baseline 3 is appropriate when the schema already fully documents the parameter.

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 clearly identifies the resource and behavior: recommended creators on the mobile app's Following page. It also clarifies that this is a creator-discovery surface returning rich user and video data rather than a bare id list. It does not distinguish itself from any specific sibling tool, which keeps it from 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?

Usage is implied by 'creator-discovery surface rather than a bare id list,' suggesting this is for discovering creators with profile and recent-video context. However, there is no explicit guidance on when to choose this over other TikTok mobile tools such as tiktok_mobile_search_user or tiktok_mobile_feed, and no exclusions are stated.

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