Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

edit_download

DestructiveIdempotent

Changes the destination folder for listed Synology Download Station tasks. Updates only the output share of completed or active downloads, requiring Download Station Task API v2.

Instructions

Edit task parameters. Currently supports destination (change the task's output share). Requires a newer Download Station (Task API v2); older versions get a clear error. This changes only the listed tasks; for global settings, use set_download_config. A finished task's file isn't moved: the reply says not changed for it.

Input Schema

NameRequiredDescriptionDefault
task_idsYesIDs of the tasks to change, from list_downloads.
destinationNoNew destination folder, share-relative (`video/Torrents`); it must already exist. The only editable field, so a call needs it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.1
    • addedInput schema / properties / destination / description
      Added value: +"New destination folder, share-relative (`video/Torrents`); it must already exist. The only editable field, so a call needs it."
    • addedInput schema / properties / task_ids / description
      Added value: +"IDs of the tasks to change, from list_downloads."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_edit_downloadOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, idempotent, destructive mutation. The description adds valuable behavior beyond annotations: API version requirements, scope limited to listed tasks, and the fact that finished tasks are not moved and report `not changed`.

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?

Four tightly written sentences, front-loaded with purpose and scope, then prerequisites, alternatives, and edge-case behavior. No filler.

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

Completeness5/5

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

Given the tool’s complexity as a mutation with no output schema, the description covers the essential context: what can be edited, API compatibility, task scoping, the global-settings alternative, and finished-task behavior. An agent can call it correctly from this.

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 task_ids and destination thoroughly. The description reinforces that destination is the only editable field, but adds little syntax or format detail beyond the schema.

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 (edit task parameters) and names the only currently supported editable field, destination. It also distinguishes the tool from the sibling set_download_config, which handles global settings.

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 says to use set_download_config for global settings and edit_download only for listed tasks. It also gives the prerequisite of a newer Download Station with Task API v2 and notes the clear error on older versions.

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

Deploy Server

Other Tools