Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_profile

Fetch a YouTube channel's profile by ID, @handle, username, or URL to get bio, join date, region, links, and stats like followers, videos, and views.

Instructions

Retrieve channel profile. Returns the profile of a YouTube channel by id, which can be a channel id, @handle, /c or /user path, bare username or full channel URL. The profile has channel id, name and URL, bio, join date, region, profile picture, links, and stats with followers_count, videos_count and views_count.

Input Schema

NameRequiredDescriptionDefault
idYesChannel ID, @handle, /c path, /user path, bare username, or full YouTube channel URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 a reasonable job: it enumerates the accepted id formats and details the return payload (name, bio, join date, region, links, and a stats object with follower/video/view counts). It omits any note on permissions or errors, but for a read-only lookup the behavioral picture is largely conveyed.

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 the core action sentence, followed by id formats and then return fields. Slightly redundant between 'Retrieve channel profile' and 'Returns the profile of a YouTube channel', but otherwise tight and 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?

No output schema exists, and the description usefully compensates by listing the returned fields including the nested stats object, so an agent knows what it gets back. For a single-parameter read tool this is nearly complete, lacking only error/precondition notes.

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% and the description's id-format list ('@handle', '/c' or '/user' path, bare username, full URL) largely restates the schema's own parameter description. Baseline 3 applies since the schema does the heavy lifting with no additional syntax or edge-case guidance.

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 and resource ('Retrieve channel profile') and enumerates the exact fields returned, so an agent can tell it apart from youtube_channel_videos, youtube_channel_playlists or youtube_channel_shorts at a glance. The channel-profile scope is unmistakable.

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 usage ('by id') but never states when to prefer this over sibling tools like youtube_channel_search, nor any preconditions. An agent can infer it is the profile lookup, but nothing is explicit.

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