Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

ACF 6.8 register-custom-post-type ability exposes an MCP schema rejected by ChatGPT/OpenAI strict validation

Abierto
  • ¿Algo no está bien?
#1,035 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php
Área
api, backend-api-design

Línea de trabajo

Comienza en src/AI/Abilities/PostType.php e inspecciona el esquema de supports junto al esquema de taxonomies. Verifica cómo se representa supports en tiempo de ejecución y, después, añade la definición de elemento que falta o reconcilia los valores documentados con estilo de objeto con el esquema publicado. Añade una comprobación de regresión automatizada que valide la ability expuesta frente a requisitos estrictos de OpenAI-compatible tool-schema.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

The ACF 6.8 acf/register-custom-post-type ability currently exposes an input schema that cannot be loaded by ChatGPT's MCP client.

When the ability is exposed as an MCP tool, ChatGPT rejects the tool during tool discovery with:

Invalid MCP tool schema for tool 'wp_ability_acf_register_custom_post_type'

I traced the issue to the schema definition of the supports property in src/AI/Abilities/PostType.php.

Environment

  • ACF PRO: 6.8.10
  • WordPress: 7.1
  • PHP: 8.3.33
  • MCP adapter: Easy MCP AI 1.7.17
  • Client: ChatGPT Custom MCP
  • Date tested: 2026-09-15

Steps to reproduce

  1. Enable ACF AI abilities:
add_filter( 'acf/settings/enable_acf_ai', '__return_true' );
  1. Expose acf/register-custom-post-type as an MCP tool.
  2. Connect the WordPress MCP server to ChatGPT.
  3. Refresh/discover MCP tools.

ChatGPT rejects the tool schema and the MCP tool refresh fails.

Suspected root cause

The current schema defines supports as an array without an items schema:

'supports' => array(
    'type'        => 'array',
    'description' => 'Features the post type supports...',
    'required'    => false,
),

However, another array property in the same ability, taxonomies, correctly includes an items definition:

'taxonomies' => array(
    'type'        => 'array',
    'description' => 'Array of taxonomy names...',
    'items'       => array(
        'type' => 'string',
    ),
    'required'    => false,
),

Strict OpenAI-compatible tool-schema validators reject array schemas without an items definition.

This is particularly problematic for an ability specifically intended to make ACF interoperable with external AI/MCP clients.

There also appears to be a contract mismatch around supports: the description/runtime behavior indicates support for both indexed arrays and associative/object-style values, while the published schema declares only type: array.

Expected behavior

acf/register-custom-post-type should expose a tool schema that can be successfully discovered and loaded by major MCP clients, including ChatGPT/OpenAI-compatible clients.

Actual behavior

Tool discovery fails when this ability is enabled.

ChatGPT displays:

Invalid MCP tool schema for tool 'wp_ability_acf_register_custom_post_type'

Disabling only the acf/register-custom-post-type MCP tool allows tool discovery to continue.

Suggested fix

At minimum, define the item type for supports:

'supports' => array(
    'type'        => 'array',
    'items'       => array(
        'type' => 'string',
    ),
    'description' => 'Features the post type supports...',
    'required'    => false,
),

The documented/runtime support for associative/object-style supports values should also be reconciled with the published ability schema.

I would also suggest adding an automated schema compatibility/regression test for all ACF Abilities exposed through MCP, particularly against strict OpenAI-compatible tool-schema validation.

This class of issue is straightforward to catch automatically before release by validating every exposed ability schema and failing CI when an array schema required by a target client is missing its items definition.

Additional observation

The same area may deserve a broader schema audit rather than treating this as a single-property typo.

For example, other ACF AI/Abilities schemas should be checked for arrays without explicit item definitions and for mismatches between runtime-supported values and the machine-readable schema.

Reproduction evidence

I can provide a screenshot of ChatGPT failing MCP tool refresh with:

Invalid MCP tool schema for tool 'wp_ability_acf_register_custom_post_type'

Reported by Süha Karalar
https://www.suhakaralar.com

Image
Lenguaje dominante
PHP
Estrellas
946
Forks
197
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AdvancedCustomFields/acf

Todos los issues de AdvancedCustomFields/acf

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.