wordpress_list_theme_filesLists all files in a WordPress theme directory recursively or non-recursively. Helps inspect theme file structure for management or debugging.
List all files in a theme directory
| Name | Required | Description | Default |
|---|---|---|---|
| theme | Yes | ||
| recursive | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does indicate a read-only operation (list), but it does not explain the effect of the 'recursive' parameter, what the return value looks like, or any potential side effects. The behavioral context is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that leads with the verb 'List' and is free of extraneous detail. It is efficient and structurally sound, although it could be slightly more informative without sacrificing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with two required parameters, no output schema, and no annotations, the description is incomplete. It does not clarify the recursive behavior, identify the expected response structure, or differentiate from similar tools. The context provided is insufficient for reliable tool selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not mention either parameter ('theme' or 'recursive'). There is no explanation of how 'theme' should be specified (slug, directory name) or what 'recursive' does. The agent receives no semantic guidance for the parameters from any source.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (List) and the resource (all files in a theme directory), making it distinct from sibling tools like wordpress_list_files (general files) and wordpress_get_themes (theme listing). It is unambiguous and directly conveys the tool's function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not mention when to use this tool versus alternatives like wordpress_list_files or wordpress_get_themes_detailed, nor does it state any prerequisites or exclusions. The agent is left to infer usage solely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.