Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tiktok_profile

Retrieve a public TikTok profile by handle to get account details and follower, following, heart, and video counts; missing, deleted, or banned handles return 404.

Instructions

Retrieve a TikTok profile. Returns a public TikTok profile by handler, the username without the leading @. The user object has the id, uniqueId, nickname, signature, verified and private flags, region, language, avatar, bio link and secUid; stats has follower, following, heart, video and friend counts. A missing, deleted or banned handle returns 404.

Input Schema

NameRequiredDescriptionDefault
handlerYesTikTok handle without the leading @

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it says the profile is public, lists the returned user and stats fields, and specifies that missing, deleted, or banned handles return 404. It leaves private-profile handling somewhat implicit, but the private flag is mentioned.

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

Conciseness5/5

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

The description is front-loaded with the core action, then gives the handle requirement, return shape, and error behavior. The field enumeration is dense but earns its place because there is no output schema.

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?

For a one-parameter profile lookup with no output schema, the description supplies enough return-field detail and error behavior for an agent to call it correctly. Nothing essential is missing given the tool's simplicity.

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 single `handler` parameter is already fully documented in the schema. The description repeats the same meaning ('username without the leading `@`') without adding syntax or format details beyond the schema, making the baseline 3 appropriate.

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: retrieve a TikTok profile. The phrase 'by `handler`, the username without the leading `@`' makes clear this is an exact-handle profile lookup, distinguishing it from sibling user-search tools like tiktok_search_user.

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?

The description gives clear usage context: call it when you have a TikTok handle and need that public profile. It does not explicitly name search alternatives or exclusions, but the exact-handle requirement sufficiently implies when this tool is appropriate.

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