Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

youtube-like-comment-viewer

Visits YouTube video links to view them for a set duration, optionally like them, and post comments across multiple URLs.

Instructions

Visit specified YouTube video links to view, like and comment. Supports multiple video links and multiple comments. Important: keyword search is not supported.

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": {
      "comments": "<comments>",
      "view_urls": "<view_urls>"
    },
    "name": "youtube-like-comment-viewer"
  }
}

Input Schema

NameRequiredDescriptionDefault
isLikeNoWhether to like videos.random
skipAdNoWhether to skip ads. Note: skipping YouTube ads may have side effects.no
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.
commentsYesComment contents to post. Multiple comments are supported; join multiple comment lines with a newline character.
viewTimeNoViewing time per video in milliseconds. Example ["2000", "3000"] means a random duration between 2 and 3 seconds.
view_urlsYesList of YouTube video URLs to operate on. Example: ["https://www.youtube.com/watch?v=DQKoNQcObn4&list=PLGCWpnvrwS15CBjWsPnG097E0IwYDXVwk&index=3"]
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
commentCountNoControls how comments are applied: 0 or empty => random comment per YouTube account (each video gets a random entry from [comments]); 1 => different accounts can comment different content (ensure number of environments equals number of comment entries).
viewIntervalNoInterval before the next video in milliseconds. Example ["2000", "3000"] means a random interval between 2 and 3 seconds.
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

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, and it never states that this performs irreversible public actions (posting comments, liking) on real YouTube accounts, nor that it drives browser environments that get closed per run. The mutation risk and account/environment expectations are only implied by schema fields like run_timeout and is_cancel_close.

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?

Three short sentences with the core action front-loaded and the critical limitation called out last. The middle sentence about multiple links/comments is mildly redundant with the schema but not wasteful enough to penalize heavily.

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

Completeness3/5

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

For a 10-parameter browser-automation tool with no annotations and no output schema, the description is thin: it does not explain what is returned, that the environment is auto-closed, or any rate/account constraints. The schema compensates for parameter detail, but the behavioral context an agent needs before committing to a mutating run is largely absent.

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 baseline is 3; the description's only parameter-adjacent content ('supports multiple video links and multiple comments') merely restates multiplicity already documented in the schema. It adds nothing about semantics of viewTime, commentCount, or env_ids beyond what the schema says.

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?

Names concrete verbs and resources — visit links, view, like, comment — and explicitly rules out keyword search, which separates it from a search-engage sibling and hints it is not the scraper. It stops short of naming a specific sibling or clarifying the relationship to the comments scraper, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

The 'keyword search is not supported' note is a useful negative constraint that steers an agent away from search-style queries. However, there is no positive when-to-use statement, no guidance on when to pick this over the sibling scraper/engage tools, and no mention that environments must be supplied via env_ids.

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