Skip to main content
Glama

mcp_check_plugin_updates

Checks for available plugin updates on a WordPress site by running Plugin Update Checker instances and a fresh WordPress.org check, returning current and new versions by source.

Instructions

Check for plugin updates now: runs every Plugin Update Checker instance (GitHub-released plugins such as the cvrt-* and wp-woo-pdf-builder; their own check otherwise runs every 12 h) and a fresh wp.org check. plugin limits the PUC run to one plugin. Returns puc_checked (slugs) and updates [{plugin, name, current, new_version, source: puc|wporg}]. Audit-logged. cvrt-mcp-endpoints 1.16.0+.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
pluginNoPlugin file path to limit the PUC check to (e.g., wp-woo-pdf-builder/wp-woo-pdf-builder.php)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the run is audit-logged, that it overrides a 12-hour schedule, which check sources are consulted (puc vs wporg), and a minimum plugin version requirement (cvrt-mcp-endpoints 1.16.0+). It stops short of saying whether the check is read-only or whether it has any side effects beyond logging, which leaves a small gap for an unannotated tool.

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?

The action and its scope are front-loaded in the first clause, and the return shape is listed compactly at the end. It is dense with parentheticals and internal jargon ('cvrt-*', 'PUC'), which costs some readability but every clause carries 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?

Although there is no output schema, the description names the returned fields (puc_checked, updates with plugin/name/current/new_version/source), so an agent knows what to expect. Audit logging and the version prerequisite are covered; the only omission is an explicit statement of whether the check mutates anything, which matters given the absent annotations.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema by explaining that 'plugin' narrows the PUC check to a single plugin rather than filtering the wp.org portion. That operational nuance is not derivable from the schema text alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check for plugin updates now') and scopes it precisely: it runs Plugin Update Checker instances plus a fresh wp.org check, as opposed to a scheduled run. It does not explicitly name the neighboring mcp_check_updates or mcp_update_plugin, so the agent must infer the boundary, which keeps it below a 5.

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?

Usage is implied rather than stated: the parenthetical that the plugin's own check 'otherwise runs every 12 h' tells the agent this tool is for forcing a check now, and the plugin parameter's limiting behavior is described. There is no explicit when-not guidance and no named alternative for core/theme updates or for acting on the results.

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