Skip to main content
Glama
Sign In
MODX MCP

MODX MCP

by rumata-estor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

modx_list_elements

List MODX elements by type (chunk, snippet, template, resource, TV, category, plugin) with optional name filtering and pagination for browsing or selecting CMS items.

Instructions

List MODX elements of a type (id + name). Supports an optional name filter and pagination.

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

Input Schema

NameRequiredDescriptionDefault
typeYes
limitNoMax results (default 100; 1–500; zero is treated as 1).
queryNoFilter by name (for resources: pagetitle/longtitle/alias).
startNoOffset for pagination.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.4

TDQS

C2.9/5.0
Behavior2/5

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

No annotations were supplied, so the description carries the full disclosure burden. It doesn't state read-only safety, whether it requires permission, how large result sets are truncated, or what the returned record shape is beyond 'id + name'. That is a meaningful gap for a 7-type listing tool with no output schema.

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?

Single compact sentence, front-loaded with verb and supported types. Partially redundant with the schema's `type` enum and param descriptions, but not verbose.

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 filterable listing tool with no mutations, this is arguably adequate, but with zero annotations and no output schema the agent is left without knowing safety, permission needs, or result shape beyond id + name. It should do a bit more given the 7-type scope.

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 75%, so the schema already documents limit, query, and start in useful detail. The description only re-states that a name filter and pagination exist, adding the note that results are id + name; it doesn't add meaning beyond the schema, e.g. how query matches across the non-resource 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 (list MODX elements of a given type) and notes the minimum payload (id + name). It does distinguish itself implicitly from modx_get_element and creation/update siblings, but does not name an alternative listing tool such as modx_list_resources, so it falls short of 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 Guidelines2/5

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

No when-to-use or when-not-to-use guidance. It never says how this differs from modx_get_element (single element), modx_list_resources (resource-only listing), modx_describe_object, or modx_search_code for discovery.

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