Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Move media

move_media
Destructive

Move one or more media assets into a specified folder, or set folderId to null to return them to the media root.

Instructions

Move one or more media assets into a folder (or to the root with folderId: null). Use list_media_folders to find the destination folderId.

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": {
      "ids": "<ids>",
      "folderId": "<folderId>"
    },
    "name": "move_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesIds of the media assets to move
folderIdYesDestination folder id, or null to move the assets back to the media root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "ids",
      +  "folderId"
      +]
  2. First observedv0.73.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds the null-folderId root behavior, but says nothing about what the move destroys or overwrites (e.g. name collisions at the destination) or whether it is reversible — relevant for a destructiveHint tool.

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 short sentences with zero filler; the action and scope come first and the follow-up tool hint comes second.

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

Completeness4/5

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

For a two-parameter mutation with a fully described schema and no output schema, this is nearly sufficient. The remaining gap is failure/overwrite behavior at the destination folder, which is meaningful because the tool is flagged destructive.

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 both parameters are already documented in structured form; the description's restatement of folderId: null and the batch nature of ids adds little beyond it. 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.

Purpose5/5

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

The description names a specific verb and resource ("Move one or more media assets into a folder") and states the batch capability plus the root-folder edge case. An agent can distinguish this from delete_media, restore_media, or list_media without opening any schema.

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?

It gives an explicit prerequisite workflow: call list_media_folders first to obtain a valid destination folderId. It does not state when-not to use it or what happens on failure, but the core when-to-use signal is clear.

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