Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete media folder

delete_media_folder
Destructive

Remove a media folder only when empty by default, or pass deleteContents to delete its assets. Use force to override the refusal that protects assets still referenced by pages, records or branding.

Instructions

Delete a media folder. By default only empty folders are removed; pass deleteContents to also delete the assets inside, and force to override the refusal that protects assets still in use.

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": "delete_media_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe folder id to delete
forceNoWhen true, delete assets that pages, records or branding still reference. The refusal names those files. Requires the media:force-delete permission.
deleteContentsNoWhen true, also delete the assets inside the folder. When false (default), deletion is refused if the folder is not empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / deleteContents / default
      Removed value: -false
    • removedInput schema / properties / force / default
      Removed value: -false
    • changedInput schema / properties / force / description
      Previous value: -"When true, delete assets that pages, records or branding still reference. The refusal names those files; pass this only after the user has seen them and said to go ahead. Requires the media:force-delete permission."New value: +"When true, delete assets that pages, records or branding still reference. The refusal names those files. Requires the media:force-delete permission."
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv0.73.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the bar is lower, but the description still adds real behavioral context: the default refuses non-empty folders and a guard blocks deletion of assets referenced elsewhere, with force as the override. The media:force-delete permission requirement lives in the schema rather than the description, and irreversibility is not stated.

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?

A single tightly constructed sentence that front-loads the default behavior and then introduces the two escalating flags. No filler or redundant restatement of the title.

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 destructive tool with full annotation and schema coverage and no output schema, this covers the safety rails an agent needs before calling. What is missing is minor: no statement that deletion is irreversible or what the response returns after a refusal override.

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 deleteContents and force are fully documented in the schema with more detail than the description provides. The description only restates the escalation path, adding no format or edge-case meaning beyond structured fields.

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 and resource (delete a media folder) and immediately scopes the default behavior to empty folders only, which separates it from delete_media on assets. It does not explicitly name any sibling tool, so differentiation is implicit rather than stated.

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?

Gives concrete when-to guidance: default call is safe for empty folders, use deleteContents to remove contained assets, and use force to override the refusal when assets are still in use. It lacks an explicit when-not-to-use statement or a named alternative for asset-only deletion.

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