Skip to main content
Glama
thenavidm

ScrapeCreators MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Top Search

tiktok_top_search

Search TikTok's Top results by query to get videos and photo carousels with captions, stats, and pagination. Requires confirm=true for credit-consuming calls.

Instructions

Searches TikTok's 'Top' results by query — returns both videos and photo carousels, unlike keyword search which only returns videos. Returns items, an array of objects each with id, desc (caption), content_type (video or photo carousel), statistics (play_count, digg_count/likes, comment_count, share_count), video info, and images for carousels. Paginate with cursor. TikTok may return duplicate results. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword to search for
cursorNoCursor to get more videos. Get 'cursor' from previous response.
regionNoNote, this doesn't filter the tiktoks only in a specfic region, it puts the proxy there. Use it in case you want to scrape posts only available for some country. Use 2 letter country codes like US, GB, FR, etc
accountNoNamed private ScrapeCreators account; selects credentials, not a remote account ID.
confirmNoMust be true for the specific approved credit-consuming research call.
sort_byNoSort by
publish_timeNoTime Frame TikTok was posted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses paid credit consumption, the confirm=true gate, duplicate results risk, the cursor pagination model, and reconciles the readOnlyHint=false annotation by explaining these are read-like POST calls that don't publish to platforms. This is exactly the extra behavioral context annotations alone cannot convey.

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 with purpose and sibling differentiation, then output shape, then operational caveats. The output-field enumeration is dense but earns its place since there is no output schema. Slightly long, but no wasted 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?

With no output schema, the description fully describes the return payload (items array with id, desc, content_type, statistics, video, images) plus pagination, duplicate caveat, and credit/confirm requirements. Nothing an agent needs to invoke it correctly is missing.

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 query, cursor, region, account, confirm, sort_by and publish_time. The description only reinforces cursor pagination and confirm semantics, adding little beyond the structured fields. Baseline 3 applies.

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?

States a specific verb and resource ('Searches TikTok's Top results by query') and immediately distinguishes itself from the sibling tiktok_search_by_keyword by noting it returns photo carousels as well as videos. An agent can pick between the two without opening either schema.

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

Usage Guidelines4/5

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

Explicitly contrasts this with keyword search and gives a clear condition for using the region proxy parameter. It does not spell out broader when-not-to-use guidance versus other TikTok search siblings (hashtag, users, suggestions), but the key routing decision is covered.

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