Skip to main content
Glama

royal-mcp__mcp_list_recent_changes

Read-onlyIdempotent

List the changes made through Royal MCP that can still be reviewed: every undo-tracked write from the last 7 days by the same WordPress user (administrators can pass all_users for every user's), newest first. Each row has the time, the tool, what it changed (target_label), what undo would restore (undo_summary), which connection made it (AI client, API key, another MCP server or a browser agent), whether it was undone, and the undo token while undo is still possible. Pass a change_id to mcp_get_change for the before and after values. Changes older than 7 days are not kept. (site: demo.royalplugins.com) Through Royally: read-only, runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "royal-mcp__mcp_list_recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoOnly changes made by this tool, for example wp_update_post.
limitNoRows to return (default 20, max 100).
sinceNoOnly changes made at or after this time: an ISO 8601 date or date-time (site time zone when no offset is given) or Unix seconds.
offsetNoRows to skip, for paging (default 0). The reply gives has_more and next_offset.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
all_usersNoAdministrators only: list every user's changes (each row names its user; undo tokens only for your own changes). Default false.
include_undoneNoInclude changes that were already undone (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip, for paging (default 0). The reply gives has_more and next_offset.",
      +  "maximum": 10000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Only changes made at or after this time: an ISO 8601 date or date-time (site time zone when no offset is given) or Unix seconds.",
      +  "type": [
      +    "string",
      +    "integer"
      +  ]
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses retention limits, ordering, permission behavior for all_users, undo-token availability, row contents, and the fact that older changes are not kept. It also confirms read-only immediate execution consistent with annotations, giving agents substantial operational context.

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?

The purpose is front-loaded and the row-field enumeration is justified because there is no output schema. Some content duplicates schema and annotation details, and the main sentence is long, but overall the description is structured and earns most of its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool without an output schema, the description is complete: it covers scope, retention, permissions, ordering, row fields, undo availability, and how to retrieve detailed before/after data. An agent has enough information to call the tool correctly and interpret its likely results.

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?

Schema description coverage is 100%, so the schema already documents all seven parameters thoroughly. The description restates some relevant behavior such as administrator-only all_users and undo-token limits, but adds little parameter meaning beyond the schema.

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: listing Royal MCP changes that are undo-tracked and still reviewable within 7 days. It adds useful scope details, including same-user filtering, administrative all_users access, and newest-first ordering, so its purpose is clear without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage boundaries: only undo-tracked writes from the last 7 days are kept, administrators can pass all_users, and the agent should use mcp_get_change with a change_id for before-and-after values. It lacks an explicit when-not or named alternative for older history, but the scope and routing guidance are strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources