Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

youtube-search-engage

Searches YouTube by keyword, selects matching results, and performs view, like, and comment actions. Direct video-link operations are not supported.

Instructions

Search YouTube for videos by keyword and perform view, like, and comment actions. Important: direct operation on specific video links 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": {
      "keyword": "<keyword>",
      "selectTitle": "<selectTitle>"
    },
    "name": "youtube-search-engage"
  }
}

Input Schema

NameRequiredDescriptionDefault
isLikeNoWhether to like videos.random
commentNoComment content; if empty, no comment will be posted.
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.
keywordYesKeyword to search for; maximum 200 characters.
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
selectTitleYesOptional title to match when selecting which search results to play, like, or comment on.
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.4/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 it mostly restates the name. It does not disclose that the tool drives real browser environments on YouTube (account/rate-limit risk), that engagement actions like likes and comments are irreversible writes, or that the run is time-bounded and the environment is torn down afterward. Those facts exist only implicitly in the schema, not in the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the capability and followed immediately by the critical limitation. Nothing is padded and the most important constraint is placed where an agent will read it.

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?

This is a 7-parameter tool that orchestrates browser environments with no output schema and no annotations, yet the description says nothing about what comes back (matched videos, per-action results, failures) or how environment selection and timeouts interact. For a multi-step automation tool with real side effects, the definition is under-specified.

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 every parameter (keyword, selectTitle, isLike, comment, env_ids, run_timeout, is_cancel_close) is already documented in structured form. The description adds no extra meaning such as how selectTitle matches against results or what the 'random' like mode does. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Search YouTube for videos by keyword') plus the follow-on actions it performs (view, like, comment), which is more than a restatement of the name. It also carves out a scope boundary by declaring that direct operation on specific video links is not supported. It stops short of naming a sibling tool, but the purpose is unambiguous.

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

Usage Guidelines4/5

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

There is a clear when-not constraint: specific video links are unsupported, so the agent must supply a keyword. What is missing is any when-to-use guidance relative to the scraper/viewer siblings (youtube-comments-scraper, youtube-like-comment-viewer), which an agent could easily confuse with this engagement tool.

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