SwiftlyMCP : Wordpress MCP Server

Discover Abilities

wp_discover_abilities

Read-only

Discover all registered WordPress Abilities (WordPress 6.9+). Abilities are self-describing plugin operations with input/output schemas and annotations (readonly, destructive, idempotent). Filter by category, namespace, or annotation type. Use this to see what plugin-specific actions are available before running them.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number for pagination
`site_id`	No	Site ID to target (optional if you have only one connected site)
`category`	No	Filter by ability category slug (e.g. "content", "commerce")
`per_page`	No	Number of abilities to return (default 50, max 100)
`readonly`	No	Filter to only read-only abilities (true) or write abilities (false)
`namespace`	No	Filter by plugin namespace (e.g. "woocommerce", "yoast")
`idempotent`	No	Filter to only idempotent abilities (true)
`destructive`	No	Filter to only destructive abilities (true) or safe abilities (false)

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 13, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Filter by ability category slug (e.g. \"content\", \"commerce\")",
+  "type": "string"
+}

addedInput schema / properties / destructive

Added value: +{
+  "description": "Filter to only destructive abilities (true) or safe abilities (false)",
+  "type": "boolean"
+}

addedInput schema / properties / idempotent

Added value: +{
+  "description": "Filter to only idempotent abilities (true)",
+  "type": "boolean"
+}

addedInput schema / properties / namespace

Added value: +{
+  "description": "Filter by plugin namespace (e.g. \"woocommerce\", \"yoast\")",
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "Page number for pagination",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / per_page

Added value: +{
+  "description": "Number of abilities to return (default 50, max 100)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / readonly

Added value: +{
+  "description": "Filter to only read-only abilities (true) or write abilities (false)",
+  "type": "boolean"
+}

removedInput schema / properties / search

Removed value: -{
-  "description": "Search term to filter abilities by name or description",
-  "type": "string"
-}

First observedOct 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description still adds real value by explaining that returned abilities carry their own input/output schemas and readonly/destructive/idempotent annotations, which tells the agent what the payload contains. Pagination behavior is left unstated.

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?

Four compact sentences, purpose front-loaded, and each sentence contributes (what it does, what abilities are, how to filter, when to use). No filler or repetition of the name/title.

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, the description usefully characterizes what is returned (schema-bearing, annotated abilities) and how to narrow results. Given 8 params at full schema coverage and annotations carrying the safety profile, the only minor gap is pagination/return-shape specifics.

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 every parameter (page, per_page, category, namespace, readonly, idempotent, destructive, site_id) is already documented in the schema. The description only restates the filter axes (category, namespace, annotation type) without adding format or interaction detail, so baseline 3 applies.

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?

States a specific verb (discover) and resource (registered WordPress Abilities), and clarifies what an Ability is (self-describing plugin operations). It reads distinctly against the sibling wp_get_ability_info, since this returns the full catalog rather than a single ability's details.

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

Usage Guidelines4/5

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

"Use this to see what plugin-specific actions are available before running them" gives clear when-to-use framing, and the filter axes are named. It stops short of explicitly contrasting with wp_get_ability_info for single-ability lookup, so no exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SwiftlyMCP : Wordpress MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?