Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

youTube-automatic-uploader

Upload YouTube videos automatically by supplying a video file path and content description, running the task in specified DICloak environments.

Instructions

Automatically upload YouTube videos. Important: provide video file path and content description.

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": {
      "env_ids": "<env_ids>",
      "content": "<content>",
      "filePath": "<filePath>"
    },
    "name": "youTube-automatic-uploader"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesDescription of the video content, such as title and description. Limit to 5000 characters.
env_idsYesOne 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.
filePathYesPath to the video file, supporting local or network URLs. Examples: https://example.com/video.mp4 or C:\Users\servi\Downloads\video.mp4. Note: use the correct path format for macOS or Windows.
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?

With no annotations supplied, the description carries the full behavioral burden, yet it only says the upload happens automatically. It does not disclose authentication requirements, video visibility defaults, external side effects, failure behavior, or what happens to the uploaded content. The brief input reminder is useful but insufficient for an external write operation.

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?

The description is two short sentences with the core action front-loaded. It is appropriately sized and contains no filler or tangential wording. The input reminder is compact even if it restates required schema fields.

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?

For an external upload tool with five parameters, no annotations, and no output schema, the description is too sparse. It omits authentication prerequisites, YouTube account/channel context, visibility behavior, environment selection meaning, and return or failure semantics. The schema covers parameter details, but the overall definition leaves significant operational questions unanswered.

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 documents all five parameters in detail. The description reinforces the file path and content fields but adds no meaning beyond the schema and does not mention env_ids, run_timeout, or is_cancel_close. Baseline 3 is appropriate 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: "upload YouTube videos" with "Automatically." This is clear enough for an agent to identify the tool's core function, though it does not clarify scope such as single-video uploads, scheduling, or visibility settings. It also does not explicitly differentiate from any sibling, but no sibling appears to serve the same upload purpose.

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 description provides an input prerequisite ("provide video file path and content description") but no when-to-use or when-not-to-use guidance. It does not mention alternatives, preconditions such as YouTube account connection, or scenarios where this tool should not be selected.

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