Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp db optimize

wordpress_wp_db_optimize
Destructive

Optimize WordPress database tables through the companion plugin, applying OPTIMIZE TABLE only to tables with the active WordPress prefix.

Instructions

[UNIFIED] Optimize WordPress database tables through the companion plugin. Runs OPTIMIZE TABLE only on tables with the current WordPress table prefix.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered by structured data. The description still earns credit for disclosing the underlying operation (OPTIMIZE TABLE) and the companion-plugin dependency, but it says nothing about table locking, execution duration, or resource cost on large databases.

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?

Two short sentences, front-loaded with the operation and its prefix restriction; nothing is redundant. The '[UNIFIED]' prefix is a tagging artifact that adds no information but costs little.

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 one-parameter maintenance tool with no output schema and annotations that already declare destructiveness, the description is close to sufficient on behavior. It still omits the site parameter's meaning and whether anything is returned or how long the operation may block.

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

Parameters1/5

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

There is a single required parameter, 'site', with 0% schema description coverage, and the description never explains what it identifies (site ID, URL, alias) or what a valid value looks like. With one documented-by-nothing parameter and no compensating text, the definition leaves the caller guessing.

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?

The description pairs the specific verb 'Optimize' with the concrete resource 'WordPress database tables' and adds a real scope constraint: only tables with the current WordPress table prefix. That distinguishes it implicitly from maintenance siblings like db_check, db_size and db_tables, though none are named.

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?

There is no when-to-use guidance and no stated alternative; the agent must infer that this is a periodic maintenance action rather than a diagnostic. The prefix scoping tells the agent what will be touched, not when to choose this tool over wp_db_check or wp_db_tables.

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