Skip to main content
Glama
Sign In
MainWP MCP Server

MainWP MCP Server

by cvsloane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mainwp_updates_plugins

Update plugins on a WordPress site. Specify site ID or domain, optionally target specific plugins, or simulate before applying.

Instructions

Update plugins on a WordPress site

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

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)
pluginsNoSpecific plugin/theme slugs to update (comma-separated). Omit to update all.

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 provided; description merely states the action without disclosing side effects, reversibility, or behavior when no updates are available.

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?

Single sentence is concise, but structure could be improved with separation of parameter details.

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

Completeness2/5

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

Lacks explanation of return values, error handling, and the effect of omitting the plugins parameter (update all vs none).

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%, so the description adds no value beyond the schema's own parameter descriptions.

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?

Description clearly states 'Update plugins on a WordPress site' with a specific verb and resource, distinguishing it from sibling tools like list, activate, or delete.

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 vs alternatives (e.g., update all vs specific plugins), no mention of prerequisites or when to enable dry_run.

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