Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update media folder

update_media_folder
Destructive

Rename a media folder and move it under a different parent folder, or pass null as the parent ID to place it at the top level.

Instructions

Rename a media folder and/or move it under a different parent folder.

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": {
      "id": "<id>"
    },
    "name": "update_media_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe folder id to update
nameNoNew folder name
parentIdNoNew parent folder id to re-parent under; pass null to move it to the top level.

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: +[
      +  "id"
      +]
  2. First observedv0.73.1

TDQS

A3.5/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 by structured data. The description adds only the 'and/or' optionality and nothing about the consequences of moving a folder (whether contained media moves with it, whether existing links break), which is the most behaviorally relevant unknown for a destructive operation.

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?

One short sentence, front-loaded with the action and with no filler. It is efficient, though a sentence on the destructive consequence of re-parenting would have earned its place.

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 three-parameter, flat-schema tool with full schema coverage and annotations covering the safety profile, the description supplies enough to select and invoke it correctly. The only meaningful gap is the side effect of moving a folder on its contents.

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 coverage is 100%, so all three parameters including the null-parentId semantics ('pass null to move it to the top level') are already documented in the schema. The description's 'and/or' reinforces that name and parentId are independently optional, but adds nothing beyond that.

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?

States a specific verb pair (rename / move) and a specific resource (media folder), which cleanly separates it from delete_media_folder, create_media_folder, and move_media. It stops short of naming those siblings, so an agent must infer the boundary from the verb+resource alone.

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?

Usage is only implied: the agent can infer it should call this when it wants to rename or re-parent a folder, but there is no explicit when-to-use or when-not guidance and no mention of the sibling move_media (which handles individual media items, not folders). Adequate but leaves a real routing ambiguity unresolved.

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