Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_mobile_feed_post

Fetch TikTok's primary mobile feed via POST and return a schema-free protobuf decode with field-number keys and string leaves, useful when no published message schema is available.

Instructions

Fetch the app's primary feed call (POST, protobuf) decoded without a schema. Calls the app's primary feed route - POST /aweme/v2/feed/, which the Android client sends with a protobuf request body and answers with protobuf - and returns a schema-free decode: field numbers become keys, length-delimited fields become strings when printable, nested messages when they parse and base64 otherwise, plus a flat list of every string leaf. Field numbering is inferred because TikTok publishes no schema for this message; use the JSON GET /tiktok/mobile/feed route when you need the stable structured contract.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it discloses the POST method, protobuf request/response format, schema-free decoding rules, field-number inference, and fallback base64 behavior. It also explains that TikTok publishes no schema for this message, which sets expectations about reliability.

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 description is dense but front-loaded: the first sentence identifies the tool's purpose, and later sentences explain the route and decoding behavior. It is appropriately detailed for a no-schema protobuf tool, though the decoding rules could be slightly more compact.

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?

There is no output schema, so the description must explain the return shape, and it does: field numbers as keys, printable length-delimited fields as strings, nested messages when parseable, base64 otherwise, plus a flat string-leaf list. Given the complexity and absence of annotations or schema, this is sufficiently complete for correct invocation and result interpretation.

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?

The tool has zero parameters, so there is no parameter semantics to explain. The baseline for zero parameters is 4, and the description correctly does not invent or discuss nonexistent inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: it fetches TikTok's primary feed via `POST /aweme/v2/feed/` and returns a schema-free protobuf decode. It also distinguishes itself from the sibling `tiktok_mobile_feed` route by identifying that route as the stable JSON alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explicitly tells the agent when to choose the alternative: use the JSON `GET /tiktok/mobile/feed` route when a stable structured contract is needed. That gives clear selection guidance between this raw decode tool and the JSON feed tool.

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