Skip to main content
Glama
Sign In
MainWP MCP Server

MainWP MCP Server

by cvsloane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mainwp_updates_list

List all pending updates across WordPress sites for core, plugins, and themes. Optionally filter updates for a specific site.

Instructions

List all pending updates across WordPress sites (core, plugins, themes)

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": "mainwp_updates_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoFilter updates for a specific site. Omit for all sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so the description alone must convey behavior. It states the tool lists updates, but does not explicitly confirm it is read-only or disclose any side effects, permissions, or rate limits. 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?

Single sentence, front-loaded with the verb 'List', contains no extraneous information. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains what the tool returns (list of pending updates) but does not specify the structure or fields of the list. Given the simplicity with one optional parameter and no output schema, it is minimally complete but could be improved.

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% for the single 'site' parameter, which is described in the schema. The description adds no additional meaning beyond the schema's description.

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 lists pending updates across WordPress sites, specifying types (core, plugins, themes). It distinguishes from sibling tools like mainwp_updates_apply or mainwp_updates_plugins by focusing on the general list of all pending updates.

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 on when to use this tool versus siblings like mainwp_updates_plugins or mainwp_updates_themes. The description implies it for a broad overview, but does not mention alternatives or exclusion criteria.

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