| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ge_url in Alt_Text_Generation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. Co-authored-by: the-hercules <thehercules@git.wordpress.org> Co-authored-by: dkotter <dkotter@git.wordpress.org> Co-authored-by: WouterP0lman <wouterpolman@git.wordpress.org> To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Sorry, something went wrong.
|
Thanks for the quick turnaround here, @the-hercules. This matches what I ran into exactly. I hit both problems while exposing the WordPress/ai abilities as MCP tools through wordpress/mcp-adapter on a local WP 7.0 + Abilities API setup:
Your approach looks right to me: keeping sanitization in the execution path and reworking the term output into a valid array-of-objects schema. The schema round-trip test is a good guard against regressions. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
What?
Closes #668
Fixes invalid JSON Schema definitions for AI abilities exposed through the Abilities API, REST, and MCP adapters.
Why?
Two ability schemas were not clean JSON Schema:
Strict consumers such as wordpress/mcp-adapter validate and traverse these schemas, so malformed or non-serializable schema values prevent these abilities from being exposed as MCP tools.
How?
Use of AI Tools
AI assistance: Yes
Tool(s): Codex / ChatGPT
Model(s): GPT-5.5
Used for: Investigating the schema failures, drafting the implementation, and updating tests. Final changes were reviewed and adjusted by me.
Changelog Entry
Ensure AI ability schemas and outputs are valid JSON Schema for strict REST and MCP consumers.