Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_resources

Lists MODX resources in the content tree, with optional filters for parent, context, deleted state, or pagetitle/alias/uri search. Returns IDs, titles, aliases, URIs, publish and folder flags.

Instructions

List resources (the content tree), optionally filtered by parent, context, deleted state, or a pagetitle/alias/uri query. Returns id, pagetitle, alias, uri, parent, template, published, deleted, isfolder, class_key, context_key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "modx_list_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 100, max 500).
queryNoFilter by pagetitle/alias/uri substring.
startNoOffset for pagination.
parentNoParent resource id (e.g. 0 for top level).
contextNoContext key (e.g. 'web').
deletedNoWhen set, filter resources by deleted state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

A3.6/5.0
Behavior3/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 does disclose the returned field set, which is genuinely useful, but it omits other behavior an agent needs: whether deleted resources are included by default when the filter is unset, pagination defaults/limits (only present in the schema), and any 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 sentences, both front-loaded: the capability and its optional filters first, the return contract second. No filler, no repetition of the tool name, nothing that could be cut.

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 present, listing the eleven returned fields is the key compensating move and it is done here. What remains missing is modest: default deleted-state behavior and pagination guidance, both of which are largely covered by the parameter schema.

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 all six parameters are already documented, including limit bounds, offset semantics, and the substring query behavior. The description restates the filter set without adding syntax or defaulting details beyond the schema, so the baseline 3 applies.

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?

The description pairs a specific verb (List) with a specific resource ('resources (the content tree)') and enumerates the filter dimensions, so the agent knows exactly what it retrieves. It does not distinguish itself from adjacent tools such as modx_bulk_resources or modx_list_elements, which keeps it below a 5.

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?

The phrase 'optionally filtered by parent, context, deleted state, or a pagetitle/alias/uri query' implies the browsing/lookup use case, but there is no explicit when-to-use statement, no exclusions, and no named alternative for finding resources another way.

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