Skip to main content
Glama

read_comment_thread

Read-only

Read the full reply thread under one YouTube comment on the signed-in user's channel: the original plus the whole back-and-forth, so you can reply in context. Call this BEFORE drafting a reply to ONE specific comment that has replies (marked [THREAD] in read_comments) and to see whose turn it is in an ongoing conversation. Do NOT call this for a general question about what people are saying or the themes across their comments; that is read_comments only. Only open a thread when you are actually about to reply to one specific comment. Use the comment's id (the 'lc=' value from its reply link). Part of Klyf Pro's reply flow.

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": {
      "comment_id": "<comment_id>"
    },
    "name": "read_comment_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesThe id of the top-level comment whose thread to read (the 'lc=' value from its reply link)

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, destructiveHint=false and openWorldHint, so safety is covered; the description contributes workflow-level behavior instead — it is a prerequisite step in the reply flow, it requires the target comment to have replies, and it is positioned within 'Klyf Pro's reply flow'. It stops short of describing reply ordering, pagination, or what an empty/absent thread looks like.

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 action and the routing rule are front-loaded in the first two sentences, and the 'do NOT' exclusion follows logically. Minor redundancy: the constraint about only opening a thread when actually replying is stated twice (once as 'so you can reply in context' / 'BEFORE drafting a reply' and again as 'Only open a thread when you are actually about to reply').

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?

For a single-parameter read with no output schema, the description covers what comes back (original plus full back-and-forth), the prerequisite (comment must have replies), and its place in the reply workflow. What it does not cover — thread size limits, ordering, or pagination of replies — is a modest gap for an agent that may need to handle long threads.

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 100% and the schema description already states 'the id of the top-level comment whose thread to read (the lc= value from its reply link)'. The description restates the same 'lc=' derivation and reinforces that it is the top-level comment id, adding emphasis but no new semantics. 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?

States a specific verb and resource — read the full reply thread under one YouTube comment on the signed-in user's channel — and immediately distinguishes scope ('one comment' vs. the entire comment section). The parenthetical 'the original plus the whole back-and-forth' makes the unit of retrieval unambiguous.

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?

Explicitly names both the when ('BEFORE drafting a reply to ONE specific comment that has replies, marked [THREAD] in read_comments') and the when-not ('Do NOT call this for a general question about themes across comments; that is read_comments only'), with the alternative tool named. It also states the gating condition that the comment must actually have replies.

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