Skip to main content
Glama
Sign In
MainWP MCP Server

MainWP MCP Server

by cvsloane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mainwp_updates_wp

Update WordPress core to the latest version on a managed site. Provide site ID or domain to apply the update.

Instructions

Update WordPress core to the latest version

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "mainwp_updates_wp"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite ID (number) or domain name (e.g., "1" or "pavinglist.com")
dry_runNoSimulate the operation without making changes (defaults to MAINWP_ENABLE_DRY_RUN_BY_DEFAULT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry behavioral information. It fails to disclose whether the update is safe, what happens if already latest, or if there are side effects (e.g., backup needed).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, but it is underspecified. It lacks important context that could be added without being verbose.

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?

For a simple tool with no output schema, the description covers the basic purpose but misses behavioral context that would help an agent use it correctly. It is minimally adequate.

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 the baseline is 3. The description adds no extra meaning beyond the schema; it does not clarify how 'site' is used or the behavior of 'dry_run'.

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 action ('Update'), the resource ('WordPress core'), and the target ('to the latest version'). It is distinct from sibling tools like mainwp_updates_plugins and mainwp_updates_themes, which target different components.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., mainwp_updates_apply). No context about prerequisites, such as needing to check current version first, or scenarios where an update might fail.

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