pom_theme_get_settings_values: read setting values
Reads what one POM Theme setting is currently set to.
Arguments
| Argument | Required | Meaning |
|---|---|---|
setting |
Yes | The setting key, from the schema |
fields |
No | Return only these field keys |
include_schema |
No | Add the field definitions to the response |
resolve_code_files |
No | Replace file references with their contents |
Permissions
mcp:read and pom_theme:read, plus edit_theme_options.
One setting per call
There is no way to read everything at once. Each call takes exactly one setting key, and an unrecognised key returns pom_ai_mcp_theme_setting_not_found.
Get the keys from pom_theme_list_settings_schema first. They are internal identifiers and do not match the labels shown in the admin.
resolve_code_files is what makes CSS and HTML readable
POM Theme stores code-typed fields — CSS, HTML, JavaScript — as files on disk, and the stored setting value is the path to the file, not the code.
So without this option, reading a setting containing custom CSS gives you a filename. With it, each such value is expanded into file, type and content.
Read the custom_css setting with resolve_code_files and show me the actual CSS.
This is the single most common confusion with this tool: a response that looks like it contains no code because it contains paths.
Code-field expansion walks nested rows. Asset selectors retain their saved references; reading a template selection does not expand its attached script or stylesheet source.
fields narrows a large response
Settings can carry dozens of fields. Passing fields filters the response to the keys you name, which matters when you only need one value and the setting is big.
Field keys that do not exist are simply absent from the result rather than an error, so a typo produces a quieter failure than a wrong setting key does. Check that what you asked for came back.
include_schema explains the values
It appends the field definitions, so you can see what a value means — which options a choice field accepts, what type each field is.
Useful when a value looks cryptic. A layout stored as sidebar-right is clear; a value of 2 is not, until the schema tells you what the options are.
An empty response is usually initialization
Settings flagged requires_initialization in the schema hold nothing until saved once from the WordPress admin. Reading one returns an empty values set.
That is not an error and not a permissions problem. Check the flag in the schema before concluding something is wrong.
Read before any write
The write tools have dry runs, but this is what tells you the field's current value, its shape, and whether it is even present.
Read post_archive with include_schema, then tell me what the sidebar layout is currently set to.
For CSS, reading first matters more: the global CSS and snippet tools replace rather than append, so this response is the content you would need to restore.
It reads more than you can write
This tool reads any setting. pom_theme_update_setting writes two fields by default.
So being able to read a value is no indication that it can be changed. Do not offer to adjust something on the strength of having read it.
Common problems
| Symptom | Cause |
|---|---|
pom_ai_mcp_theme_setting_not_found |
Wrong setting key; check the schema |
pom_ai_mcp_forbidden |
Missing edit_theme_options |
| Values look like file paths | Use resolve_code_files |
An empty values set |
The setting has never been initialized |
| A field you asked for is missing | Wrong field key; no error is raised |
content is empty for a code field |
The file is missing or outside the settings directory |
Related
pom_theme_list_settings_schema— get the keyspom_theme_get_global_css— the shortcut for global CSSpom_theme_update_setting