Crawlora MCP

youtube_profile

Read-only

Fetch public profile details for one YouTube channel by channel ID. Use youtube_channel_videos to list that channel's uploaded videos.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "youtube_profile"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	YouTube video id, or channel id/handle/URL depending on the endpoint.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data properties are covered. The description adds little beyond 'public profile' – no mention of auth requirements, rate limits, or what data is returned. With annotations present, the bar is lower, but this adds minimal value.

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?

Two short, front-loaded sentences with zero waste. The primary action is stated first, followed by the alternative tool suggestion.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values need not be explained. However, the description resolves an important ambiguity: the parameter name is 'id' and the schema says it can be a video ID, while the description targets a channel. It should more clearly reconcile that this endpoint expects a channel identifier.

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 parameter's meaning is fully documented in the schema. The description only says 'by channel ID' whereas the schema notes the id can also be a handle or URL, adding a small clarification but not compensating beyond baseline.

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 (Fetch) and resource (public profile details for one YouTube channel), and explicitly distinguishes from the sibling youtube_channel_videos. The scope (public profile, by channel ID) is unambiguous.

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

Usage Guidelines4/5

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

Names a specific sibling and its use case (listing uploaded videos), which helps route the agent. However, it doesn't mention other plausible alternatives like youtube_channel_search or youtube_channel_shorts, nor does it state when NOT to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?