Skip to main content
Glama

mcp_get_audit_log

Retrieve a newest-first audit trail of state-changing MCP calls on a WordPress site, including cron, Action Scheduler, and update-check activity with masked context.

Instructions

Audit trail of state-changing MCP calls on this site (cron runs, Action Scheduler runs, update checks), newest first: time, action, user, context (secret-masked). The site keeps the newest 200. cvrt-mcp-endpoints 1.16.0+.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
limitNoHow many entries (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses ordering (newest first), the retention cap (newest 200), the returned fields (time, action, user, masked context) and a minimum plugin version. It does not say whether the call is read-only or what permissions are needed, but the nature of an audit log makes that largely self-evident.

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 tight sentences plus a version note; the resource and ordering are front-loaded and there is no filler. The version-compatibility tag is minor clutter but justifies itself for callers checking feature availability.

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 two-parameter read tool with no output schema and no annotations, the description covers return contents, ordering, retention and version gating well enough to call correctly. Only the safety/permission profile is left implicit.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: 'newest first' defines how limit selects entries, and 'the site keeps the newest 200' explains why limit caps at 200 and what happens to older records. The site parameter itself is left to the schema.

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 resource and scope: an audit trail of state-changing MCP calls, with the exact event classes named (cron runs, Action Scheduler, update checks). This clearly separates it from live-status siblings like mcp_get_cron_status or mcp_get_action_scheduler, though no sibling is named explicitly.

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?

Usage is implied by the scope statement – fetch this when you need a historical record of state-changing calls rather than current status. There is no explicit when-to-use/when-not guidance and no pointer to the alternative tools for live cron or scheduler data.

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