Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

tiktok_posts

Retrieve posts from a TikTok profile by secUid, with pagination and sorting by latest, popular, or oldest. Use the returned cursor to fetch the next page.

Instructions

Retrieve posts from a TikTok profile. Lists posts from a TikTok profile identified by secUid. sort_type is 0 latest (default), 1 popular or 2 oldest. cursor defaults to 0. The response has itemList, hasMore and a cursor to pass back to fetch the next page.

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor
secUidYesTikTok secUid for the profile
sort_typeNoSort mode: 0 latest, 1 popular, 2 oldest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort_type / enum
      Added value: +[
      +  0,
      +  1,
      +  2
      +]
  2. Addedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses pagination mechanics and the response shape (itemList, hasMore, cursor to pass back) plus defaults, but says nothing about auth requirements, rate limits, or whether the call is read-only beyond the implied 'Retrieve'.

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-loaded and efficient, covering purpose, sort modes, cursor default, and the response shape in a few sentences. The first two sentences are slightly redundant in restating that posts come from a profile.

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 does the right thing by naming the returned fields and the pagination loop. Combined with 100% schema coverage, an agent has enough to call it correctly, though auth/prerequisite context is absent.

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 all three parameters and the sort enum. The description largely restates the enum meanings and adds the cursor default of 0, so it sits at the baseline rather than adding meaningful new semantics.

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 posts from a TikTok profile') and narrows it to a profile identified by secUid. It does not explicitly distinguish itself from the many tiktok_* siblings (tiktok_profile, tiktok_search_user, tiktok_post), leaving the agent to infer the difference, but the resource is unambiguous.

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 only implied: give a secUid, get that profile's posts. There is no explicit when-to-use/when-not guidance and no pointer to a sibling for obtaining the secUid (e.g., tiktok_search_user), which would be the natural prerequisite.

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