pom_theme_get_custom_css: read managed custom CSS
Lists POM Theme's named CSS snippets, with their contents.
Arguments
None. It returns every snippet.
Permissions
mcp:read and pom_theme:read, plus edit_theme_options.
What it returns
items, one per snippet. Each carries:
| Field | Meaning |
|---|---|
repeater_identifier |
The snippet's ID — needed to update or delete it |
stylesheet_name |
The human label |
css_code |
The stored file and its resolved content |
last_change |
When it was last written, as a timestamp |
Contents are resolved for you, so you get the actual CSS rather than a file path.
repeater_identifier is the handle for everything else
Both pom_theme_upsert_custom_css and pom_theme_delete_custom_css work by identifier. This is the only tool that tells you what they are.
They are generated strings, not names. Working from a stale list is how the wrong snippet gets overwritten:
List the CSS snippets and show me each identifier with its name.
Get them fresh before any write.
Names are not unique
Nothing stops two snippets being called "Header fixes". The identifier distinguishes them; the name does not.
So a request phrased as "update the header snippet" is ambiguous whenever a duplicate exists. Match on the identifier, and if two snippets share a name, say so rather than picking one.
last_change tells you what is live work
The timestamp is written on every save through these tools. A snippet changed this morning is probably someone's in-progress work; one untouched for two years is probably safe to consolidate.
It is the only signal of recency available — snippets have no author and no revision history.
Snippets versus the global stylesheet
Both end up in the same compiled output. The difference is how they are managed:
- The global stylesheet is one blob. Every write replaces all of it.
- Snippets are individually addressable. A write touches one and leaves the rest alone.
That makes snippets the safer place for anything separable. This listing is how you find out which model a site actually uses — a site with one giant global stylesheet and no snippets is one where every CSS change is high-risk.
Order does not equal cascade priority you can rely on
Snippets are compiled into the site's stylesheet, and CSS cascade rules apply to the result. If two snippets set the same property on the same selector, which wins depends on the compiled order and specificity, not on the order they appear in this listing.
Do not resolve a conflict by reordering. Make the intended rule more specific, or consolidate the two snippets.
Reading before writing
Snippets have no revisions. This response is the only record of a snippet's content before an upsert replaces it.
List the snippets, then show me the full CSS of the one called "Campaign banner".
Using it well
Auditing:
List every CSS snippet with its name, identifier and size, and tell me which look redundant.
Diagnosing:
Which snippet contains a rule for
.site-header?
That second question is answerable because contents are resolved — you can search across all snippets in one call.
Common problems
| Symptom | Cause |
|---|---|
| The tool is missing | POM Theme is not available |
pom_ai_mcp_forbidden |
Missing edit_theme_options |
| An empty list | No snippets exist; check the global stylesheet |
| A snippet's content is empty | Its file is missing or unreadable |
| Two snippets with the same name | Allowed; use the identifiers |
| Styling on the site is not in any snippet | It is global, Customizer, or plugin CSS |