Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp theme file list

wordpress_specialist_wp_theme_file_list
Read-only

List files in a WordPress theme directory with relative paths, sizes, MIME types, SHA-256 hashes, and modified times; filter by glob and cap results at 1000 files.

Instructions

[UNIFIED] List files inside a theme directory. Walks wp-content/themes/{theme_slug} and returns each file's relative path, size, mime, sha256, and modified_at (epoch). Optional glob filters by fnmatch pattern (default **/*). Capped at 1000 files per call (S-18); when the walk truncates, the response carries truncated: true. Requires Airano MCP Bridge v2.14.0+.

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": {
      "site": "<site>",
      "theme_slug": "<theme_slug>"
    },
    "name": "wordpress_specialist_wp_theme_file_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
globNo**/*
siteYes
max_filesNo
theme_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.1/5.0
Behavior5/5

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

The description adds a lot that the single `readOnlyHint: true` annotation does not: the exact filesystem root walked, the 1000-file cap, the `truncated: true` signal when the walk is cut short, and a minimum bridge version (v2.14.0+). The read-only claim is consistent with the annotations, and the truncation behavior is exactly the kind of operational detail an agent needs to interpret an incomplete result.

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?

The description is dense and front-loaded: capability first, then scope, then return shape, then limits. Nearly every sentence carries unique information, but references like "(S-18)" and the trailing version requirement are cryptic filler that do not help an agent act.

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 and only a `readOnlyHint` annotation, the description does the heavy lifting well: it enumerates returned fields (relative path, size, mime, sha256, modified_at) and explains truncation. It falls short on the `site` parameter, on any auth or permission requirements, and on how to page past the 1000-file cap.

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 0%, so the description must carry the parameter semantics, and it only partly does. `glob` is well served (fnmatch pattern, default `**/*`), and `max_files` is implied by the 1000-file cap, but that cap is never tied to the parameter by name, and `site` is left completely unexplained. `theme_slug` is only implied through the path template.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("List files inside a theme directory") and then narrows the scope to `wp-content/themes/{theme_slug}`, which cleanly separates it from the theme-level sibling `wp_theme_list` and from the per-file siblings like `wp_theme_file_read`/`wp_theme_file_write`. An agent can tell exactly what this returns without opening any schema.

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?

Usage is only implied by the scoping sentence: an agent infers this is the tool to reach for when it needs to enumerate a theme's files rather than read or modify one. There is no explicit when-to-use statement, no named alternative, and no statement of when this tool should not be used.

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