Skip to main content
Glama

OnlyChili AI Cinema & Series Catalog

get_channel

Read-onlyIdempotent

Fetch public creator channel profile, bio, follower count, video count, and canonical 8-locale channel URLs by handle.

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": {
      "handle": "<handle>"
    },
    "name": "get_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesCreator channel handle (with or without leading @).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful shape information — the response carries profile, bio, counts, and localized URLs — but says nothing about error behavior for an unknown handle or whether counts are cached or live, which is the remaining behavioral gap.

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?

A single front-loaded sentence with the verb first, the resource second, and the payload enumerated after. Every clause carries information — no restatement of the title and no filler.

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?

There is no output schema, so the description reasonably takes on the job of naming the returned fields, including the less obvious 8-locale canonical URLs. It is nearly complete for a one-parameter read tool; only failure behavior for a nonexistent handle is unstated.

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?

With one parameter at 100% schema description coverage, the schema already explains that the handle may include a leading @. The description confirms the call is keyed by handle and that results are channel-scoped, but adds no formatting, casing, or lookup-resolution detail beyond the schema, so baseline 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?

The description pairs a specific verb ("Fetch") with a specific resource ("public creator channel profile") and enumerates what is returned: bio, follower count, video count, and canonical 8-locale channel URLs. It is clearly a channel-level lookup keyed by handle, which is distinguishable from the video- and series-oriented siblings without opening any schema.

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?

Usage is only implied by the mechanics of the call — supply a handle, get that channel's profile. There is no explicit statement of when to prefer this over search_videos or list_latest_videos, and no mention of preconditions such as the channel needing to exist or be public, though "public creator channel" hints at the constraint.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources