Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_youtube_creators_search

Search public YouTube creator profiles by keyword, region, subscriber/video/view counts, bio links, join date, and discovery source to filter and sort channel datasets.

Instructions

Search the YouTube creators dataset. Searches public YouTube channel profiles stored in a search index — subscriber, video and view counts, region, bio and links, discovered via Common Crawl and Wikidata and hydrated from each channel's public About page. Sort enum: relevance, followers_desc, followers_asc, views_desc, videos_desc, hydrated_at_desc, hydrated_at_asc. Some channels hide their subscriber, video, or view count; the _available flags on each item distinguish a hidden count (stored as 0, *_available: false) from a genuine 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over channel_name and bio, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, followers_desc, followers_asc, views_desc, videos_desc, hydrated_at_desc, hydrated_at_asc
regionNoExact channel region/country filter (case-insensitive), max 128 characters
has_bioNoFilter by a non-empty About bio
has_linksNoFilter by at least one linked external URL
max_viewsNoMaximum total view count
min_viewsNoMinimum total view count
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
channel_idNoExact channel id filter (e.g. UCxxxxxxxxxxxxxxxxxxxxxxxx), max 128 characters
max_videosNoMaximum uploaded-video count
min_videosNoMinimum uploaded-video count
joined_afterNoChannels created on or after this date (RFC3339 or YYYY-MM-DD)
joined_beforeNoChannels created on or before this date (RFC3339 or YYYY-MM-DD)
max_followersNoMaximum subscriber count
min_followersNoMinimum subscriber count
hydrated_afterNoRecords last refreshed on or after this date (RFC3339 or YYYY-MM-DD)
hydrated_beforeNoRecords last refreshed on or before this date (RFC3339 or YYYY-MM-DD)
discovery_sourceNoExact filter for how the channel was discovered (e.g. commoncrawl, wikidata), max 128 characters
views_count_availableNoFilter by whether the channel has a known total view count
videos_count_availableNoFilter by whether the channel has a known uploaded-video count
followers_count_availableNoFilter by whether the channel exposes a public subscriber count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "followers_desc",
+  "followers_asc",
+  "views_desc",
+  "videos_desc",
+  "hydrated_at_desc",
+  "hydrated_at_asc"
+]
  2. Addedv1.16.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains that some channels hide counts, and that the `_available` flags distinguish hidden counts from genuine zeros—a key behavioral nuance for interpreting results. It also notes the data sources and hydration process. However, it does not mention pagination constraints, rate limits, or explicitly confirm read-only semantics, which are minor omissions for a search tool.

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 moderately long but each sentence contributes: it states the purpose, lists the searched fields and data sources, enumerates sort options, and explains the hidden-count behavior. It repeats the sort enum that is also in the schema, but that is a minor redundancy. The structure is logical and front-loaded with the core purpose.

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 search tool with 22 parameters and no output schema, the description covers the essential aspects: what is searched, sort options, and the hidden-count nuance. It does not describe the output structure beyond mentioning the `_available` flags, nor does it mention pagination limits (max page_size, total cap), but those are documented in the schema. Given the complexity, it is reasonably complete.

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 schema already documents each parameter. The description adds value by explaining the meaning of the sort enum values and, crucially, clarifying the semantics of the `_available` boolean parameters (hidden count vs. genuine zero). This goes beyond the schema's bare descriptions and helps the agent use filters correctly.

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 opens with 'Search the YouTube creators dataset,' a specific verb plus resource. It then enumerates the fields searched (subscriber, video, view counts, region, bio, links) and the data provenance, making the tool's purpose unmistakable. The name and verb clearly distinguish it from sibling tools like datasets_youtube_creators_item and datasets_youtube_creators_facets.

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

Usage Guidelines2/5

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

The description does not state when to use this tool versus alternatives, nor does it mention any conditions that would make it inappropriate. There is no reference to sibling tools or to cases where another search should be used. The intended use is implied by the description, but no explicit guidance is provided.

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