Skip to main content
Glama
CreatorDB

creatordb-mcp-server

Official
by CreatorDB

list_youtube_niches

Retrieve CreatorDB's full YouTube niche taxonomy with over 14,000 subcategories and channel counts per niche. Ideal for understanding YouTube creator classification.

Instructions

List the full YouTube NICHE taxonomy used by CreatorDB — every available niche (14000+ entries) with channelCount per niche. NICHES are granular subcategories (e.g. "Vlog/People Blogs", "ASMR/People Blogs"). To see which niches a specific creator is classified under, use get_youtube_profile and read the niches field. Per-platform: YT/IG/TT each have their own niche taxonomy — they are not interchangeable. Takes no parameters. Costs 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses cost (1 credit) and no parameters, but does not specify response structure or pagination. However, for a simple list tool, this is adequate.

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?

Highly concise; every sentence earns its place. The purpose is front-loaded, with details and guidance following efficiently.

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 zero-parameter tool with no output schema, the description is complete. It covers what the tool does, what data it returns, when to use alternatives, and cost.

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 exist, so baseline is 4. The description adds value by specifying output includes channelCount and gives examples, which enriches understanding beyond the empty schema.

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?

The description clearly states it lists the full YouTube NICHE taxonomy with 14,000+ entries and channelCount per niche. It distinguishes from platform-specific sibling tools (list_instagram_niches, list_tiktok_niches) and provides examples.

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

Usage Guidelines5/5

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

Explicitly tells when to use (list all niches) and when not (to see a specific creator's niches, use get_youtube_profile). It also warns that per-platform taxonomies are not interchangeable.

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