Captapi

tiktok_channel_posts

Latest videos from a TikTok profile, cursor-paginated. Flat 2 credits; failures are 0 credits. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

Name	Required	Description
`url`	Yes	TikTok profile URL, @handle, or username, e.g. https://tiktok.com/@username. Not a YouTube channel URL. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble.
`cache`	No	Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
`limit`	No	How many of the creator's latest videos to return on this page (default 20, max 200). Newest first. Flat 2 credits per successful call.
`cursor`	No	Pagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response (TikTok's max_cursor timestamp, e.g. 1783614676000). A null nextCursor means the end of the list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / limit / description

Previous value: -"How many of the creator's latest videos to return on this page (default 20, max 200). Newest first. Native serves cost a flat 2 credits; extended serves scale with returned posts — 1 credit per 20, minimum 2 (200 posts = 10 credits)."New value: +"How many of the creator's latest videos to return on this page (default 20, max 200). Newest first. Flat 2 credits per successful call."

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / limit / description

Previous value: -"How many of the creator's latest videos to return on this page (default 20, max 200). Newest first. Flat 2 credits per call."New value: +"How many of the creator's latest videos to return on this page (default 20, max 200). Newest first. Native serves cost a flat 2 credits; extended serves scale with returned posts — 1 credit per 20, minimum 2 (200 posts = 10 credits)."

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / cache / description

Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."

Changed4 schema fields changedAug 20, 2026

changedInput schema / properties / cache / description

Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response."New value: +"Pagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response (TikTok's max_cursor timestamp, e.g. 1783614676000). A null nextCursor means the end of the list."

changedInput schema / properties / limit / description

Previous value: -"Max items to return. Default 20, max 200. Flat 2 credits per call."New value: +"How many of the creator's latest videos to return on this page (default 20, max 200). Newest first. Flat 2 credits per call."

changedInput schema / properties / url / description

Previous value: -"TikTok profile URL, e.g. https://tiktok.com/@username. Not a YouTube channel URL. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."New value: +"TikTok profile URL, @handle, or username, e.g. https://tiktok.com/@username. Not a YouTube channel URL. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."

Changed1 schema field changedJul 18, 2026

changedInput schema / properties / limit / description

Previous value: -"Max items to return. Default 20, max 200. Billed per result."New value: +"Max items to return. Default 20, max 200. Flat 2 credits per call."

Changed1 schema field changedJul 18, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Pagination cursor. Leave empty for the first page; then pass the nextCursor value returned in the previous response.",
+  "type": "string"
+}

Changed1 schema field changedJul 16, 2026

changedInput schema / properties / cache / description

Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."

Changed1 schema field changedJul 15, 2026

addedInput schema / properties / cache

Added value: +{
+  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
+  "type": "boolean"
+}

Changed1 schema field changedJul 4, 2026

changedInput schema / properties / url / description

Previous value: -"TikTok profile URL, e.g. https://tiktok.com/@username."New value: +"TikTok profile URL, e.g. https://tiktok.com/@username. Not a YouTube channel URL. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."

First observedJun 7, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose billing behavior beyond the schema: flat 2 credits, failures and empty results free, and a 24h cache that is off by default. It still omits auth requirements, rate limits, and whether a failed partial page is charged, but the cost model is genuinely informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The credit/charge rule is stated three times in slightly different words ('Flat 2 credits; failures are 0 credits', 'Costs 2 credits', 'Empty results and failures are never charged'), which is pure redundancy. The first sentence is well front-loaded, but roughly half the text is repeated and could be compressed to one clause.

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

Completeness3/5

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

With no output schema and no annotations, the description should carry more, and it does cover cost, caching, and pagination, which are the main things needed to call it correctly. It stops short of describing the returned item shape (video fields, thumbnail/URLs) or end-of-list behavior beyond the schema's nextCursor note, leaving a modest 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 all four parameters (url, cache, limit, cursor) are already documented in the schema, including cross-platform URL warnings and cursor semantics. The description only restates cache/cost behavior, adding no parameter detail beyond what the schema already provides, so the baseline 3 applies.

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 first clause names a specific resource and verb ('Latest videos from a TikTok profile') and adds pagination behavior, so an agent knows exactly what it retrieves. It does not name or contrast with close siblings like tiktok_channel_details or tiktok_user_followers, so sibling differentiation is left implicit.

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: the cursor/pagination hints that this is the tool for enumerating a profile's video feed, and the cache note hints at cost-saving reuse. There is no explicit when-to-use versus alternatives and no exclusion conditions naming other TikTok endpoints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Captapi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

tiktok_channel_posts

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources