Skip to main content
Glama

read_comments

Read-only

Read and summarize the audience's YouTube comments for the signed-in user's channel: the themes viewers keep raising or asking for, what the audience wants, needs, struggles with, or their pain points and problems (as voiced in comments), and how many comments are unanswered. Call this when the user asks what their audience wants or struggles with, what people are saying or commenting about, what themes come up, or about unanswered comments. Pass video (a title or part of one) when they ask about ONE upload's comments, like 'what are people saying on my IBKR video' or 'any questions on my latest tutorial'; omit it for the whole channel. For WHO the audience is (age, location, how they find you), use analyze_audience; for what video to make next, use suggest_ideas. 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": "read_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
videoNoOne upload to read the comments of, given as its title or part of it; omit for the whole channel

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds the operationally important fact that it reads the real connected channel with no input and no clarification round-trip. It also previews the summary content (themes, wants, unanswered counts), which is behavior beyond the annotations. It does not mention cost, latency, or limits on how many comments are scanned, which is the only remaining gap.

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?

Front-loaded with the action and scope, and the routing sentences earn their place. Some redundancy: the audience-needs list ('wants, needs, struggles with, or their pain points and problems') restates itself, and the closing anti-clarification sentence is emphatic to the point of being wordy.

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 carries the return-value burden and does describe what the summary contains. For a zero-required-parameter read tool this is largely complete; the unexplained `title` parameter and no mention of what happens with zero or ambiguous matches are the only shortfalls.

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 coverage is only 50%. The description fully compensates for `video` — title-or-partial-title matching, per-upload scope, and what omitting it means — with concrete examples. But the `title` parameter is completely unaddressed in both description and schema, leaving one of two parameters unexplained.

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 — 'read and summarize the audience's YouTube comments' — plus the scope (signed-in user's channel) and the exact outputs (recurring themes, audience wants/pain points, unanswered comment count). It explicitly separates itself from analyze_audience (who the audience is) and suggest_ideas (what to make next), so an agent can route without opening schemas.

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 explicit trigger phrases ('what their audience wants', 'what people are saying', 'what themes come up', 'unanswered comments') and names the alternative tools for adjacent questions. It even resolves the one-video-vs-whole-channel decision rule and forbids a common failure mode (asking the creator for context or a link) before calling.

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