Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_get_custom_css_revision

Read-onlyIdempotent

Reads one Additional CSS revision after validating the active stylesheet and current Custom CSS parent post.

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>",
      "revision_id": "<revision_id>"
    },
    "name": "wp_get_custom_css_revision"
  }
}

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.
revision_idYesSelected revision ID from wp_list_custom_css_revisions.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds a real behavioral detail beyond annotations: the call validates the stylesheet and parent post before reading, implying a guarded/failing read. It does not state what happens when validation fails (error type) or what the response contains.

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 tight sentence with the action front-loaded and the validation qualifier trailing. No filler, though the phrase 'Additional CSS' plus 'Custom CSS' is slightly redundant and could be compressed.

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 simple, idempotent single-record read with full schema coverage and clear annotations, nearly everything the agent needs is present. The only gap is the absence of any statement about the returned content (revision CSS body, metadata), which matters since 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%, so all four parameters are documented in the schema, including their upstream sources. The description reinforces that stylesheet and parent_post_id are expected current values rather than arbitrary inputs, but adds no format or edge-case meaning beyond that. 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?

The description states a specific verb and resource: 'Reads one Additional CSS revision'. It also names the validation subject (active stylesheet and current Custom CSS parent post), which distinguishes it from wp_list_custom_css_revisions and wp_restore_custom_css_revision without naming them 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 rather than stated: 'one revision' signals a single-item fetch following a listing, and the schema names wp_get_custom_css and wp_list_custom_css_revisions as prerequisite sources. However, the description never explicitly says when to use this versus wp_get_custom_css or the restore sibling, so the agent must infer the workflow.

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