pom_theme_get_global_css: read global CSS
Reads POM Theme's global custom stylesheet — the one that applies everywhere.
Arguments
None.
Permissions
mcp:read and pom_theme:read, plus edit_theme_options.
What it returns
| Field | Meaning |
|---|---|
file |
Where the stylesheet is stored on disk |
content |
The CSS itself |
Unlike pom_theme_get_settings_values, this tool resolves the file for you — no resolve_code_files option needed. It is the convenient shortcut for the one stylesheet people ask about most.
An empty content has two meanings
Either no global CSS has been written, or the file it points to is missing or unreadable.
file distinguishes them: an empty file means nothing was ever saved; a populated file with empty content means the file is gone. The second case matters — it means CSS the site expects to be applying is not.
Content is also returned empty if the path falls outside the settings directory, which is a safety check rather than a fault.
This is the whole stylesheet, and the write replaces it
pom_theme_update_global_css does not append. Whatever you send becomes the entire global stylesheet.
So this read is not optional before a write — it is the only copy of what would be lost:
Read the global CSS and show me all of it. I want to keep it before making a change.
Keep the response somewhere outside the conversation. There are no revisions for theme settings.
Global versus snippets
POM Theme has two places for custom CSS, and they behave differently:
| Global CSS | Snippets | |
|---|---|---|
| How many | One | Many |
| Read with | This tool | pom_theme_get_custom_css |
| Identified by | Nothing; there is only one | A repeater identifier and a name |
| Best for | Site-wide overrides | Named, separable pieces of styling |
If a site's custom styling is one long global stylesheet, every change rewrites all of it. Splitting it into snippets makes individual changes safer, and is worth suggesting before a large edit.
It is not the WordPress Customizer CSS
WordPress has its own Additional CSS, edited in the Customizer. That is a different store, POM AI does not read or write it, and CSS can be present in one and absent from the other.
If styling on the site does not appear in this response, check there. See Native custom CSS.
Nor is it the generated stylesheet
website.min.css is the compiled output that includes the theme's own styles plus your custom CSS. It is read with pom_theme_get_generated_css.
This tool reads your source; that one reads the build result. Diagnosing "my CSS is not applying" usually means comparing the two.
Using it well
Read the global CSS and summarise what it does.
Before an edit:
Read the global CSS, then show me the exact block you propose to change.
Common problems
| Symptom | Cause |
|---|---|
| The tool is missing | POM Theme is not available |
pom_ai_mcp_forbidden |
Missing edit_theme_options |
Empty file and content |
No global CSS has been saved |
Populated file, empty content |
The file is missing or unreadable |
| Styling on the site is not here | It is in snippets, the Customizer, or a plugin |
| The CSS here is not taking effect | Check the generated stylesheet and the cache |
Related
pom_theme_update_global_css— replaces this entirelypom_theme_get_custom_css— the snippetspom_theme_get_generated_css— the compiled result