Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Audit hook disable

wordpress_audit_hook_disable
Destructive

Clear the companion plugin's audit-hook configuration and stop forwarding events; requires manage_options to remove endpoint URL, secret, and event settings.

Instructions

[UNIFIED] Clear the companion plugin's audit-hook configuration (endpoint_url, secret, events) and stop forwarding events. Requires manage_options.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description does add real value beyond that by naming exactly what is destroyed (endpoint_url, secret, events) and that forwarding stops, plus the manage_options requirement. It stops short of stating whether already-forwarded events are retained or whether the configuration must be fully re-entered to restore forwarding.

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?

A single front-loaded sentence that puts the destructive action and its exact targets first, with the auth requirement trailing. The '[UNIFIED]' prefix is pure noise and the only removable element.

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?

For a one-parameter destructive tool with no output schema, the definition covers what is removed, that event forwarding ceases, and the required capability. Only the site-parameter meaning and the post-call state (does forwarding resume automatically?) are left unaddressed.

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?

There is one parameter, 'site', with 0% schema description coverage, and the description says nothing about it. Low coverage means the description should compensate by clarifying what site identifier is expected, and it does not.

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: it clears the companion plugin's audit-hook configuration (naming endpoint_url, secret and events) and stops event forwarding. The 'configure/status/disable' naming family makes it separable from wordpress_audit_hook_configure and wordpress_audit_hook_status, though no sibling is explicitly named.

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 ('Requires manage_options') but no when-to-use framing: it never says to check wordpress_audit_hook_status first, nor when to disable versus reconfigure. Usage is implied by the verb rather than stated.

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