Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Discover plugin abilities

discover_abilities
Read-only

Find registered WordPress plugin abilities to invoke them safely instead of writing directly to database tables. Filter by name or description to locate the capability you need.

Instructions

List the abilities registered on the site through the WordPress Abilities API — capabilities that plugins such as WPForms, AIOSEO or SeedProd expose for programmatic use. Running a plugin's own ability is always safer than writing to its tables directly, because the plugin's validation, hooks and cache invalidation still run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoFilter abilities by name or description.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description need not repeat safety. It adds context about the underlying API and the rationale for using abilities, which goes beyond the annotations. However, it does not disclose behavior like pagination or output structure, but given the read-only nature and annotations, this is acceptable.

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?

Two sentences with no fluff. The first sentence front-loads the primary function; the second provides valuable context about why abilities are preferable, though it's slightly tangential to a listing tool. Still, it earns its place by aiding decision-making. Appropriately sized.

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?

For a simple read-only list operation with optional search and site_id, the description conveys the purpose and the broader ecosystem. It does not explicitly describe the return format (a list of abilities) but that is implied. Given the output schema is absent, this is sufficient. It could mention pagination or that details are available via get_ability_info, but that is not strictly necessary.

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 coverage is 100%: both search and site_id have clear descriptions. The tool description does not add any parameter-specific details beyond what the schema provides, so it sits at the baseline for high schema coverage. No extra guidance on parameter usage is given.

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 clearly states the verb (list) and resource (abilities) with a specific API (WordPress Abilities API). It names example plugins (WPForms, AIOSEO, SeedProd) and distinguishes this from sibling tools like discover_content_types or discover_taxonomies by focusing on abilities. The purpose is unambiguous.

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 description explains the broader value of abilities (safer than direct table writes) but does not explicitly say when to use this tool versus alternatives like get_ability_info or run_ability. It implies listing is a discovery step but lacks direct guidance on when to choose this tool over siblings. No exclusions or conditions are given.

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