kiro fails to properly use postman powers - schema mismatches and json validation errors

[avonBP]

Out of the box, Kiro (Claude Opus 4.5) is struggling to use this power. I provided a folder structure, list of requests, urls, parameters, and envs and instructed Kiro to create the collection.

After multiple aborted attempts, I manually provided the postman 2.1.0 schema to kiro as a local steering document. However - following the schema documentation did not help.

I then created a sample collection in postman by hand, and instructed Kiro to use getCollection to view it and use it as a guide - also without success. I've managed to create a collection, and add a simple GET request, I've been able to create environment variables as well. Otherwise I'm having very little success creating a collection regardless of json/object structure.

I'd request that the MCP server fully utilize the published 2.1.0 standard for the collection object and sub-objects. ty.

edit: further testing hints that this may simply be an issue with folders. it looks like the MCP server validation is expecting both "request" and "item" properties on each [item] of a collection. The valid schema should be "request" for requests and "item" for folders, and they are mutually exclusive.