💡 Request - Surface content type field validations (e.g. array size limits) before write

[markferritto]

Is your feature request related to a problem? Please describe.
The blockBadPractices content type has a hard maximum of 6 items in its badPractices array. The AI built a payload with 7 entries and only discovered the constraint when the publish call failed with a validation error. By then, all 7 entries were saved as drafts and the user had to decide which one to drop on the spot. Field validations (including array size limits) are not surfaced before the write, so the AI can’t validate payloads proactively.

Describe the solution you'd like

• When fetching an entry or content type definition, expose content type field validations — including array size limits, required fields, and link constraints.
• Ensure get_content_type returns validation metadata in a format the AI can use to validate payloads before calling update_entry or create_entry.
• Constraints should be visible before the write, not discovered at publish time.

Describe alternatives you've considered

• Relying on AI instructions to call get_content_type before write — not enforced by the tool.
• Adding more detailed docs — helps but doesn’t prevent validation errors.

Additional context
Reported after an incident where a payload exceeded the limit and validation failed at publish.

[tylerpina]

Hey there Mark Ferritto (@markferritto), thank you for bringing this feature request to our attention! I have brought this request up to our product team and we are engaged in discussions on whether this feature should be prioritized. I'll give you an update when we reach a decision.