Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

youtube-comments-scraper

Scrape comments from a specified YouTube video URL to gather comment data for analysis or export. A video URL is required.

Instructions

Scrape comments from a specified YouTube video. Important: a video URL is required.

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": {
      "url": "<url>"
    },
    "name": "youtube-comments-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesVideo URL (retrieveable on desktop); must start with https://
countNoNumber of comments to scrape.
env_idsNoOne or more environment IDs where this task should run. If the user did not provide environment details (name, id, remark, serial number), prompt for them or offer to help create an environment.
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
is_cancel_closeNoShould the environment be closed after the execution is completed? 0 means close, 1 means do not close. The default is 0. If you set it to 1, please set run_timeout to 0 to avoid automatic closing due to timeout.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does very little with it: it says nothing about read-only versus mutating behavior, rate limits, authentication, how many comments come back, ordering, or what happens when the environment is closed. For a network-scraping tool that spins up an environment (env_ids, run_timeout), the absence of those operational notes is a real 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?

Two short sentences, front-loaded with purpose and with the requirement emphasized. Slightly redundant phrasing ('specified' plus the URL restatement) keeps it just short of exemplary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description is the only place an agent could learn what a scrape returns (fields, ordering, pagination, failure modes) and how the environment lifecycle parameters behave. It supplies none of that, leaving an agent unable to predict results beyond 'some comments'.

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 description coverage is 100%, so the schema already explains url, count, env_ids, run_timeout, and is_cancel_close in more detail than the description does. The description merely restates that the URL is required and adds no meaning about count limits, environment selection, or timeout interaction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb plus resource ('Scrape comments from a specified YouTube video'), so an agent knows exactly what it retrieves. It does not, however, draw any boundary against nearby siblings such as youtube-like-comment-viewer or youtube-subtitle-scraper, leaving the differentiation to the names alone.

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

Usage Guidelines2/5

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

The only guidance is the prerequisite 'a video URL is required', which is really a required-parameter note already visible in the schema. There is no statement of when this tool is preferable to a sibling scraper, nor any exclusion or alternative path.

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