Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_get_custom_css

Read-onlyIdempotent

Reads WordPress Additional CSS for the active theme. Use this for persistent CSS source-of-truth inspection instead of browser-injected style tags.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoDefaults to rendered. Use persisted before exact-text editing; its css matches persisted_css_sha256.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
stylesheetNoOptional theme stylesheet slug. Defaults to the active stylesheet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that this targets the active theme's Additional CSS rather than rendered output, which is genuine context. It does not mention behavior when no Additional CSS exists, whether output is raw text, or what happens for a non-active stylesheet.

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?

Two tight sentences with the resource front-loaded and the usage rule immediately after. No redundant restatement of the name or of schema fields, and nothing an agent must skip past to reach the point.

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 single-resource read with a fully documented schema and complete annotations, the description is close to sufficient. Since there is no output schema, a brief note on what is returned (CSS text, empty result when unset) would close the remaining gap.

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 site_id, stylesheet, and the rendered/persisted enum with the sha256 tie-in. The description adds nothing parameter-specific; 'for the active theme' implies the stylesheet default but does not expand on it. Baseline 3 applies when the schema does the heavy lifting.

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 verb and resource: 'Reads WordPress Additional CSS for the active theme.' It also distinguishes the subject matter from a plausible confusion ('browser-injected style tags'). It does not name the nearest siblings (wp_get_custom_css_revision, wp_list_custom_css_revisions), so differentiation from those is left implicit.

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?

Gives clear when-to-use guidance — 'Use this for persistent CSS source-of-truth inspection' — plus an explicit exclusion of browser-injected style tags. It stops short of routing to revision-listing or update tools, and does not mention the rendered vs. persisted choice, which the schema carries instead.

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