Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

datasets_creators_item

Retrieve one stored public TikTok creator profile by creator_uid, optionally including inactive accounts or entitled contact email data.

Instructions

Get one stored TikTok creator. Retrieves one public TikTok creator profile by creator_uid. Deleted/private accounts remain hidden unless include_inactive=true. Contact email stays redacted by default and include_email=true is honored only for entitled non-Free API keys.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "creator_uid": "<creator_uid>"
    },
    "name": "datasets_creators_item"
  }
}

Input Schema

Name	Required	Description
`creator_uid`	Yes	Exact creator_uid from a search result, e.g. tiktok:@handle
`include_email`	No	Return stored contact email only for entitled non-Free API keys
`include_inactive`	No	Include deleted/private accounts for historical lookup

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose non-obvious behavior: default hiding of deleted/private accounts, historical-lookup semantics of include_inactive, and an entitlement gate on email exposure. It omits return shape and any rate-limit or auth details beyond the email entitlement rule, so it is strong but not exhaustive.

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?

Three front-loaded sentences with the identifier and scope stated first and the access rules after; nothing is wasted. The first two sentences overlap somewhat ('Get one stored TikTok creator' / 'Retrieves one public TikTok creator profile'), a minor redundancy.

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?

For a single-item read tool with full schema coverage and no output schema, the definition covers the identity parameter, the two visibility/entitlement behaviors, and the default state. What is missing (returned fields, auth requirements for the key itself) is modest given the tool's simplicity.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds value by stating the default behavior (accounts 'remain hidden unless' the flag is set) and the exact entitlement condition under which include_email is honored. It does not add format or syntax guidance for creator_uid beyond what the schema already says.

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 ('Get one stored TikTok creator', 'Retrieves one public TikTok creator profile by creator_uid') and makes the singular, by-identifier scope explicit, which cleanly separates it from sibling search/facets tools like datasets_creators_search and from the YouTube counterpart.

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?

Gives clear conditions for the optional flags (inactive accounts hidden unless include_inactive=true; email only for entitled non-Free keys), which tells an agent when each switch applies. It stops short of explicitly routing to a sibling (e.g., use search to obtain a creator_uid), so it is clear context without stated alternatives.

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

Deploy Server