Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_list_custom_css_revisions

Read-onlyIdempotent

Lists revision metadata for the active theme Additional CSS post without returning full revision CSS.

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_id": "<site_id>",
      "stylesheet": "<stylesheet>",
      "parent_post_id": "<parent_post_id>"
    },
    "name": "wp_list_custom_css_revisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
stylesheetYesExpected active theme stylesheet slug from wp_get_custom_css.
parent_post_idYesExpected current Custom CSS post ID from wp_get_custom_css.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered. The description's one added fact — that it returns metadata rather than full revision CSS — is genuinely useful since there is no output schema, but it says nothing about ordering, pagination, or why stylesheet/parent_post_id are needed for a read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the resource and containing no filler. The qualifying clause at the end is the most decision-relevant detail and costs only a few words.

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 three-parameter read tool whose parameters are fully documented and whose annotations cover the safety profile, the definition covers the essentials, including the key return-content distinction. It is slightly thin on what the returned metadata contains and whether results are paginated or ordered, which matters given there is no output schema.

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% and each parameter already documents its provenance ('returned by list_sites', 'from wp_get_custom_css'), so the schema carries the full burden. The description adds no parameter meaning beyond what is in the schema; baseline 3 applies.

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?

Specific verb ('Lists') plus a precisely scoped resource ('revision metadata for the active theme Additional CSS post'), and the trailing clause 'without returning full revision CSS' implicitly separates it from wp_get_custom_css_revision, which would return the full payload. It stops short of naming that sibling, so it is clear but not maximally differentiated.

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 'metadata only, not full CSS' framing implies the intended workflow (enumerate revisions, then fetch or restore one), but there is no explicit when-to-use vs when-not statement and no mention of the prerequisite that site_id, stylesheet and parent_post_id must come from list_sites / wp_get_custom_css. Guidance is inferable rather than stated.

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources