Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp plugin update

wordpress_specialist_wp_plugin_update
Destructive

Updates an installed WordPress plugin to the current wp.org version, returning an up-to-date status instead of an error when no update exists.

Instructions

[UNIFIED] Update an installed plugin to the latest wp.org version. Companion checks the cached update_plugins transient + runs Plugin_Upgrader::upgrade(). Returns no-op (with up_to_date: true) when no update is available rather than erroring. Requires Airano MCP Bridge v2.15.0+ and update_plugins.

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>",
      "slug": "<slug>"
    },
    "name": "wordpress_specialist_wp_plugin_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it discloses that the cached update_plugins transient is checked, that Plugin_Upgrader::upgrade() runs, and that a no-update case returns a no-op with up_to_date:true instead of erroring. It does not mention backup/rollback or the risk that overwriting the plugin directory may break a customized plugin, which matters given destructiveHint=true.

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?

Front-loads the action and version target, then adds return and prerequisite notes; every sentence carries information. The [UNIFIED] tag and internal class name are slightly noisy but not wasteful.

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?

No output schema, and the description does explain the no-op/up_to_date return shape and prerequisites, which is good. But for a destructive, non-idempotent mutation with two undocumented parameters, the absence of parameter meaning leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters, so the description must carry their meaning. It only hints that the target is a wp.org plugin (implying slug format), and never explains what site refers to (URL, alias, ID) or the slug format.

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: update an installed plugin to the latest wp.org version. The word "installed" implicitly separates it from the install_from_slug / install_from_zip siblings, but no sibling is named, so the differentiation is left to inference.

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 prerequisite (Bridge v2.15.0+ and update_plugins) and implies usage via "installed plugin", but never says when to prefer this over install_from_slug or what to do if the plugin isn't installed yet. No explicit exclusions.

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