Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_youtube_creators_search

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…

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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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.5/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does so well: it discloses the credit-based billing model with a per-record cost and a minimum of 2, and explains that hidden counts are stored as 0 with `*_available: false`. That cost/semantics context is genuinely hard to derive elsewhere. It omits rate limits and does not discuss pagination behavior beyond what the schema states.

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?

Front-loaded with purpose, then data provenance, sort options, availability semantics, and billing. Every sentence carries information, though the sort enum is duplicated verbatim from the schema and could be dropped. Dense but well ordered.

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 22-parameter search tool with no output schema and no annotations, the description supplies the important missing context: data provenance/hydration, sort semantics, the availability-flag encoding, and billing cost. Pagination offset limits are left to the schema but are documented there. Reasonably complete.

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 schema already documents all 22 parameters, and the baseline of 3 applies. The description restates the sort enum (redundant with the schema) but does add real meaning for the three `*_count_available` filters by explaining the hidden-vs-genuine-zero encoding. Net value over the schema is modest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and a specific resource (public YouTube channel profiles in a search index), and enumerates the searchable facets (subscriber, video, view counts, region, bio, links). An agent can tell this is the search entry point of the youtube_creators dataset. It does not explicitly distinguish itself from the sibling facets/item tools, keeping it short of a 5.

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?

No explicit when-to-use or when-not guidance. It never mentions the sibling `datasets_youtube_creators_facets` or `datasets_youtube_creators_item`, nor when to prefer faceting first versus retrieving an item by channel_id. Usage is only implied by the verb 'Search'.

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