Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Audit hook status

wordpress_audit_hook_status
Read-only

Read a WordPress site's audit-hook configuration to check endpoint, secret presence, enabled state, event list, last push time, and failure count for monitoring and troubleshooting.

Instructions

[UNIFIED] Read the companion plugin's audit-hook configuration (v2.7.0+): current endpoint_url, whether a secret is set, enabled flag, event list, last-push timestamp, failure count. Secret is never returned in full — only the last 4 characters. 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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, yet the description still adds real behavioral context: the secret is redacted to the last 4 characters, manage_options is required, and the feature only exists on plugin v2.7.0+. That is meaningful disclosure beyond the annotation, with only return-shape/pagination caveats left unstated.

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?

One dense sentence, front-loaded with the [UNIFIED] tag and the action verb, then a compact field list. Every clause earns its place, though the long comma chain makes it a slightly run-on read.

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 small read-only tool with no output schema, the description effectively serves as the return-value contract by listing every field. The only shortfall is the unexplained 'site' parameter, which is the sole required input.

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?

The single parameter 'site' has 0% schema description coverage and the description never mentions it, so an agent gets no help on what a site identifier looks like or whether it is a slug, URL, or ID. With low coverage the description is expected to compensate and it does not.

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?

States a specific verb+resource ('Read the companion plugin's audit-hook configuration') and then enumerates exactly what comes back: endpoint_url, secret-set flag, enabled flag, event list, last-push timestamp, failure count. The 'Read' framing makes it trivially distinguishable from the sibling audit_hook_configure and audit_hook_disable tools.

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?

Provides a concrete prerequisite ('Requires manage_options') and a version gate (v2.7.0+), which help an agent decide if the call is viable. However, it never says when to prefer this over siblings or when it would be pointless to call, so usage is only implied by the read-vs-write naming.

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