Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_create_media_folder

Create a folder inside a MODX media source, at the root or under a specified parent directory. Use it to organize uploaded files and assets with clear names and paths.

Instructions

Create a folder inside a media source. source = id/name, parent = parent directory (default root), name = folder name.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
parentNo
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a mutation but says nothing about required permissions, behavior when the folder already exists, whether the parent path is auto-created, or what is returned on success or failure.

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 sentence for the action followed by compact inline parameter clarifications. Front-loaded and free of filler, though the parameter gloss could be formatted more scannably.

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

Completeness3/5

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

For a 3-parameter mutation tool with no annotations and no output schema, the description covers the inputs adequately but leaves behavioral gaps: error conditions, permission requirements, and idempotency are all unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it explains that `source` accepts an id or name, that `parent` is the parent directory defaulting to root, and that `name` is the folder name. This meaningfully exceeds the bare schema types.

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 folder inside a media source.' This clearly distinguishes it from siblings like modx_create_media_file and modx_delete_media_folder, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus modx_create_media_file or other media tools, and no prerequisites stated (e.g. whether the parent must already exist or whether the source must be writable). The only usage-adjacent content is the parameter gloss.

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