wp_get_term_meta: read a permitted custom field
Use this operation for an identified content field. Internal plugin storage, credentials, permission settings, script configuration and keys beginning with an underscore are excluded. An empty or omitted key never returns a metadata dump.
Arguments
| Argument | Required | Meaning |
|---|---|---|
term_id |
Yes | Target term ID |
key |
Yes | One permitted field key |
Requirements
The authenticated user needs manage_categories, the taxonomy's edit capability and access to this term metadata. The connection needs the corresponding read scope.
A key must be a WordPress-registered term field exposed through REST on a public taxonomy. The target must be supported content in this site. Site administrators can inspect field definitions in the native administration interface; do not guess internal keys.
Use and verify
- Identify the field from its supported native definition.
- Read that explicit key on the intended term.
- Inspect its value and use the owning feature's contract to interpret it.
The response contains meta, the single stored value. An absent field can return an empty value.
pom_ai_mcp_meta_denied means the key, target or metadata permission is outside this operation. Use dedicated tools for SEO, featured images, layouts and script assignment. A write gate or capability error requires the site owner to grant the intended access. Field changes are not a site-wide undo mechanism; retain the previous value when recovery matters.
Related: MCP security and access.