Skip to main content
Glama
Sign In

SelieeAI

by io.github.neebloltd
OverviewDiscussionsAdmin

Get YT Channel

get_yt_channel
Read-onlyIdempotent

[read] One YouTube channel's profile only (no videos; YouTube Data API v3, through the merchant's Google account). Give the channel_id (UC..., the channel_id of a video row) or the username (the handle, @ optional, a youtube.com/@handle or /channel/ address also works; an exact match). Answers channel: channel_id, title, custom_url, description (up to 5000 characters: where a channel writes its contact details), country, published_at, thumbnail, banner, keywords, subscriber_count (null when hidden), video_count, view_count, url. The About page's business e-mail is not in the API. One call is one priced read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
usernameNo
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that calls run through the merchant's Google account, that each call is one priced read, that subscriber_count is null when hidden, and that the About page's business e-mail is not exposed by the API. These are exactly the operational facts an agent needs and are not implied by readOnlyHint/idempotentHint.

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?

Purpose and scope are front-loaded in the first sentence, and the field enumeration earns its space because no output schema exists. The dense parentheticals and mid-sentence line breaks make it slightly harder to scan than it needs to be, but there is no filler.

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

Completeness5/5

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

Covers everything an agent needs for a two-parameter read with no output schema: input formats, the full return-field inventory, nullability of hidden counts, known data exclusions, and the pricing model. Nothing material is left to inference beyond parameter precedence.

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 description coverage is 0%, so the description carries the full burden and mostly succeeds: it gives the `UC...` prefix for channel_id, notes you can lift a channel_id from a video row, and lists accepted username forms (handle, optional `@`, full youtube.com URL) with exact-match semantics. The one gap is that it never states whether both parameters may be supplied or which wins, despite both being nullable with zero required.

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 (fetch one YouTube channel's profile) and explicitly scopes out videos, so it can be distinguished from list_videos, list_yt_popular, and search_yt_trends. The `[read]` tag plus the named backend (YouTube Data API v3) makes the operation unambiguous on first read.

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?

Clearly conveys when this fits (single-channel metadata lookups) and what it does not return (videos), which is the key boundary against the video/trend siblings. It does not name an alternative such as yt_insights_channel for channel analytics, so the agent must infer that distinction from the sibling list.

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

All SelieeAI toolsInspect
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