Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_youtube_creators_item

Fetch a YouTube creator's channel record from the dataset by channel_id to get profile, bio, region, links, and subscriber, video, and view counts; returns 404 if absent.

Instructions

Get a YouTube creator from the dataset. Returns one YouTube channel from the dataset by channel_id. The record has channel name and URL, bio, region, join date, links, profile picture, and subscriber, video and view counts, each with an availability flag. A channel not in the dataset returns 404.

Input Schema

NameRequiredDescriptionDefault
channel_idYesYouTube channel id, e.g. UCxxxxxxxxxxxxxxxxxxxxxxxx

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 and does well: it enumerates the returned fields, notes the per-field availability flags, and explicitly states the 404 behavior for channels not in the dataset. It does not mention auth, rate limits, or pagination, but for a single-record lookup this is a solid disclosure.

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?

Three sentences that are front-loaded with purpose, then return contents, then error behavior. Efficient and free of filler, though the return-field enumeration is a touch long.

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?

No output schema exists, so the description correctly compensates by describing the record's fields and the availability flags, plus the 404 case. An agent has enough to call it correctly; only the absence of guidance on sourcing channel_id leaves a minor gap.

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 coverage is 100% and the single parameter is fully documented in the schema (with an example format). The description only restates that lookup is by channel_id, adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 (Get) and resource (a YouTube creator/channel) with the identifying key (channel_id). The item-retrieval framing clearly distinguishes it from the sibling datasets_youtube_creators_search and datasets_youtube_creators_facets tools.

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

Usage Guidelines3/5

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

The description implies the item-lookup use case by requiring channel_id, but never explicitly says when to use this vs the search sibling or that channel_id must first be obtained from a search. Usage is inferable but not stated.

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