Handsome Hosting

Update WordPress core

wp_core_update

Destructive

Update WordPress itself to the latest version and upgrade the database; can take a few minutes. The answer names the newest backup point (latestBackup), which a restore approval can put back. Refusals: not-live, migration-open, deploy-open, busy, failed.

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": {
      "serviceId": "<serviceId>"
    },
    "name": "wp_core_update"
  }
}

Input Schema

Name	Required	Description	Default
`serviceId`	Yes	the id of a service on this account

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / serviceId / description

Previous value: -"the service id from list_services"New value: +"the id of a service on this account"

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the destructiveHint annotation, the description adds duration ('can take a few minutes'), output significance (latestBackup can be restored via approval), and explicit refusal states. It does not fully explain failure recovery or permission requirements, but it substantially improves behavioral understanding.

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?

The description is three compact sentences, front-loads the action and duration, then covers output semantics and refusals. Every sentence contributes useful information without repetition.

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?

Given the destructive update behavior, the description covers duration, backup/restore context, and refusal states, and an output schema exists so return format need not be explained. It is nearly complete, though it could say more about prerequisites or the relationship to rollback/backup_now.

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?

There is one parameter, serviceId, and schema description coverage is 100%, so the input schema already explains it. The description adds no parameter-specific meaning beyond what the schema provides, which matches the baseline for high schema coverage.

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 states a specific verb and resource: update WordPress itself and upgrade the database. The phrase 'WordPress itself' distinguishes core updates from sibling plugin/theme tools such as wp_plugin and wp_theme.

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 implies usage by naming the operation and listing refusal states like not-live, migration-open, deploy-open, busy, and failed. However, it does not explicitly say when to choose this tool over alternatives such as wp_status, backup_now, or rollback.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Handsome Hosting tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?