Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Create media folder

create_media_folder

Create a media folder to organize assets, with optional parent nesting. Pass the returned folder ID to upload_media or move_media.

Instructions

Create a media folder for organizing assets. Returns the folder, whose id can be passed to upload_media (folderId) or move_media.

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

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name
parentIdNoParent folder id to nest under (omit for a top-level folder)

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

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, a non-destructive mutation, so the bar is lower. The description usefully discloses that the folder object is returned and that its id feeds other tools, but stays silent on behaviors an agent would care about: duplicate-name handling, ID prefix/method constraints for upload/move, or permission requirements.

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 tight sentences with zero filler: purpose first, then the returned value and how to use it. Every clause carries information.

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?

With no output schema, the description correctly compensates by stating what is returned and how the id is consumed. For a simple two-param create tool this is close to complete; only edge-case behavior (name collisions, invalid parentId) is uncovered.

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% with only two params, both documented in-schema (name and parentId with 'omit for top-level'), so the baseline applies. The description adds nothing about parentId nesting or name constraints beyond what the schema already states.

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 ('Create a media folder') plus its purpose ('for organizing assets'). It also names the downstream consumers, so an agent can place it in a workflow, though it does not contrast with siblings like update_media_folder or list_media_folders.

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 follow-up routing: the returned id can be passed to upload_media (folderId) or move_media. That's clear actionable context, but there is no explicit 'use this when' or exclusion relative to other creation tools.

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