Skip to main content
Glama
CreatorDB

creatordb-mcp-server

Official
by CreatorDB

list_tiktok_niches

Retrieve the complete TikTok niche taxonomy with channel counts per niche. Use this to explore granular subcategories for creator analysis.

Instructions

List the full TikTok NICHE taxonomy used by CreatorDB — every available niche with channelCount per niche (the response is large: ~10K+ entries). NICHES are granular subcategories (e.g. "Capcut/All", "Dance/All"). To see which niches a specific creator is classified under, use get_tiktok_profile and read the niches field. Per-platform: TT/YT/IG each have their own niche taxonomy — they are not interchangeable. TikTok does NOT have a "topics" taxonomy (that is YouTube-only) and does NOT have a per-brand sponsorship endpoint. Takes no parameters. Costs 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: large response (~10K+ entries), credits cost, no parameters, and per-platform taxonomy distinctions. Also clarifies what TikTok does not have, preventing misuse.

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?

The description is dense and informative but slightly long as a single paragraph. Every sentence earns its place, but a structured format (e.g., bullet points) could improve scannability. Still concise overall.

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?

Given no output schema and no parameters, the description covers all necessary aspects: purpose, usage, behavioral traits, and differentiators. Fully complete for a list endpoint.

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?

No parameters, so baseline 4. Description adds value by explaining the behavior and constraints, even though schema provides full coverage (no params).

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?

Description clearly states it lists the full TikTok niche taxonomy with channel counts, distinguishes from sibling tools like list_youtube_niches by specifying per-platform taxonomies, and clarifies TikTok does not have 'topics'.

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?

Provides clear context: to see a creator's niches use get_tiktok_profile, warns about large response size, and mentions it costs 1 credit. Does not explicitly list when not to use but given alternatives, it is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CreatorDB/creatordb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server