WordPress MCP Server

Liste Widgets

wp_list_widgets

List all active widgets in your WordPress sidebars to review placement and manage widget areas.

Instructions

Zeigt alle aktiven Widgets in den Sidebars an

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_list_widgets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`widgets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only operation via 'zeigt' and states that it lists active widgets, but it does not disclose any additional behavioral traits such as return format, limitations, or side effects. Adequate but minimal.

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?

The description is a single short sentence that directly conveys the function without any filler. It is concise and well-structured.

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?

The tool is simple with no parameters and an output schema present, so return values are covered. The description fully captures the core purpose. It could be enhanced by noting alternatives or exclusions, but it is complete enough for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the schema coverage is 100% vacuously. With no parameters to document, the description does not need to add parameter meaning, and the baseline for zero params is 4.

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 tool displays all active widgets in sidebars, using a specific verb ('zeigt') and resource ('aktiven Widgets in den Sidebars'). It distinguishes from siblings like wp_list_sidebars and elementor_list_widgets by specifying 'active widgets in sidebars'.

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?

No explicit guidance is given on when to use this tool versus alternatives. The usage is implied from the purpose but there are no exclusions or comparisons to sibling tools such as elementor_list_widgets.

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

Deploy Server