Skip to main content
Glama

acf_get_post_field

Retrieves a single Advanced Custom Fields value from a WordPress post by site, post ID, and field name, with formatted or raw output options.

Instructions

Get a single ACF field value for a post

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": "<site>",
      "post_id": "<post_id>",
      "field": "<field>"
    },
    "name": "acf_get_post_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
fieldYesField name or key (lowercased by the endpoint)
formatNoformatted (default): values as get_field returns them; raw: unformatted stored values
post_idYesPost ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.14.0
    • changedInput schema / properties / field / description
      Previous value: -"Field name"New value: +"Field name or key (lowercased by the endpoint)"
    • addedInput schema / properties / field / pattern
      Added value: +"^[a-zA-Z0-9_-]+$"
    • removedInput schema / properties / format / default
      Removed value: -"formatted"
    • addedInput schema / properties / format / description
      Added value: +"formatted (default): values as get_field returns them; raw: unformatted stored values"
    • changedInput schema / properties / post_id / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "post_id",
      -  "field"
      -]New value: +[
      +  "site",
      +  "post_id",
      +  "field"
      +]
  3. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses very little beyond the word "Get." It does not say what happens when the field is missing, whether the return can be an array/object depending on field type, the default for the format parameter, or any auth/site requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words and a clear verb-object structure. Its brevity borders on under-specification rather than being padded, so it scores well on structure but is not exemplary in content density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple four-parameter read tool with full schema coverage, the description covers the core purpose adequately. With no output schema, however, it should explain what a returned value can look like (scalar, array, or field-type-dependent) and the missing-field behavior; that gap leaves it only minimally complete.

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 all four parameters (site, post_id, field, format) are already documented in the schema, including the formatted-vs-raw enum. The description adds nothing beyond what the schema provides, making the baseline 3 appropriate.

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: "Get a single ACF field value for a post." An agent can tell this retrieves one field value rather than a whole field set. However, it never names the closely related sibling acf_get_post_fields (plural) or contrasts the two, so the differentiation is only implied by the word "single."

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only signal is the adjective "single," which weakly implies narrow single-field retrieval versus a bulk sibling, but an agent must infer that entirely on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools