Skip to main content
Glama

list_channels

Read-only

List the YouTube channels this creator has connected to Klyf, and say which one Klyf is currently working with. Call this when the user asks which channels they have connected, which channel Klyf is using or answering about, whether Klyf can see their other channel, or how many channels they have on Klyf. This lists the channels connected TO KLYF, which is not the same as every channel on their Google account: Klyf cannot see those. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.

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": "list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds genuinely non-obvious behavior: it reads the creator's real connected channel directly, it cannot see unconnected Google-account channels, and it requires no user-supplied context before calling.

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?

The core purpose and the Klyf-vs-Google-account distinction are front-loaded, and the trigger list is compact. The closing 'not for context, not for a link, not for a title you could look up' is somewhat repetitive emphasis that could be trimmed to one clause without losing meaning.

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?

For a zero-argument read tool with no output schema, the description covers what it returns (the connected channel list plus the currently active one), when to invoke it, and the main misconception it must prevent. An agent has everything needed to call it correctly on the first turn.

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?

There are zero parameters, so the baseline is 4, and the description reinforces this by stating 'Needs no input' and warning against asking the user for context, a link, or a title. Nothing further about arguments is needed or missing.

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 gives a specific verb and resource ('List the YouTube channels this creator has connected to Klyf') plus a secondary output ('say which one Klyf is currently working with'). It also draws a scope boundary the agent could otherwise get wrong: these are channels connected to Klyf, not every channel on the Google account.

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?

It enumerates four concrete user phrasings that should trigger this call (which channels are connected, which one Klyf is using, whether Klyf can see another channel, how many channels). It does not contrast against the sibling switch_channel or state when this tool should not be used, so it stops short of full when/when-not/alternative coverage.

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