Skip to main content
Glama

diagnose_channel

Read-only

Diagnose the signed-in user's YouTube channel. Returns a ranked, prioritized list of which videos to fix first, at which funnel stage (packaging, retention, or audience fit), and what each is costing. This is the core Klyf tool; call it when the user asks what to fix or improve on their channel. It is a per-VIDEO worklist: for what the channel is about, who it serves, and the one constraint holding it back, call audit_channel instead. 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": "diagnose_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description doesn't need to re-argue safety; instead it contributes real behavioral context: the tool reads the user's actually-connected channel, requires zero input, and returns a prioritized rather than exhaustive ranking. What it leaves implicit is what "costing" is measured in and whether results are cached or rate-limited, so it stops short of full transparency.

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 return shape are front-loaded, then routing, then the no-input behavior — a sensible order. The closing emphasis ("not for context, not for a link, not for a title you could look up; call it immediately") repeats the earlier "never ask the creator anything first," which is redundant prose but defensible as an anti-hedging instruction the agent must not soften.

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?

With no output schema, the description must sketch the return value, and it does: a ranked, prioritized per-video list with funnel-stage attribution and a cost figure. Given a zero-parameter, read-only tool that is otherwise self-contained, the only gap is that the exact fields and ranking criteria of the response are not enumerated.

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 schema carries nothing to explain. The description reinforces this usefully by stating "Needs no input: it reads their real connected YouTube channel directly," which tells the agent not to fabricate arguments — no meaning beyond that is needed.

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 ("Diagnose ... YouTube channel") and immediately specifies the return shape: a ranked worklist of videos to fix, tagged by funnel stage (packaging, retention, audience fit) and cost. It explicitly contrasts itself with audit_channel (per-video worklist vs. channel identity/constraint), so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("call it when the user asks what to fix or improve"), names the alternative and the condition that selects it (audit_channel for what the channel is about / who it serves / the binding constraint), and adds a hard negative instruction about not soliciting user input first. This is about as complete as usage routing gets.

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