Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_forms

List all Ninja Forms on a WordPress site to view available forms and use their IDs for further management tasks.

Instructions

List Ninja Forms on the site (requires Ninja Forms plugin)

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_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

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 burden of behavioral disclosure. 'Requires Ninja Forms plugin' is a useful dependency disclosure, and 'List' implies read-only enumeration. It does not state what happens if the plugin is missing or describe the returned data, but the basic behavior for a simple list operation is conveyed.

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, front-loaded sentence that states the action, resource, and plugin prerequisite without any unnecessary words. Every part adds useful information.

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 zero-parameter list operation, this description is largely complete: it names what is listed and the required condition. It does not explain the output format or failure behavior when the plugin is absent, but the simplicity of the tool and absence of parameters reduce the need for more detail.

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 input schema has zero parameters, so there are no parameter semantics for the description to clarify. The zero-parameter baseline applies, and no additional parameter-level detail is needed.

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 a specific verb ('List') and resource ('Ninja Forms on the site'), and names the required plugin. This differentiates it from getters and related tools like wp_get_form, wp_list_form_submissions, and wp_list_form_webhooks.

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 gives a clear prerequisite: the Ninja Forms plugin must be installed. However, it does not explicitly contrast this tool with alternatives such as wp_get_form or wp_list_form_submissions, so when-to-use guidance is primarily implied by the name and phrasing.

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