searchNews output validation fails: News schema requires rest_id but API returns id #16

Summary

searchNews can fail output validation because the hosted OpenAPI spec and live News API response shape appear to disagree.

Observed

The hosted OpenAPI spec declares:

• News.required = ["rest_id"]
• News.properties includes rest_id
• News.properties does not include id

But NewsFieldsParameter exposes id, and live /2/news/search responses include id without rest_id.

Live API behavior matches news.fields, so the hosted News schema looks like the stale side.

Impact

Because XMCP passes the hosted OpenAPI spec to FastMCP for tool generation, this schema mismatch can cause searchNews responses to fail validation with:

Output validation error: 'rest_id' is a required property

Possible fix

The root fix may be to update the hosted OpenAPI schema. I also opened draft PR #15 with a narrow XMCP-side normalization if a client-side compatibility fix is useful.