It looks like this is a limitation of the Composer 1.5 model when handling large MCP tool responses. The data is clearly coming from the Figma MCP, you can see that in the UI, but Composer 1.5 seems to either truncate it or parse it incorrectly. Claude and GPT handle it fine.
For now, the best workaround for Figma related tasks is to switch to Sonnet 4.6, Opus 4.6, or GPT 5.3 Codex, which it looks like you are already using.
Could you grab the Request ID from the Composer 1.5 chat where this happened? Click the three dot menu in the top right of the chat, then Copy Request ID. That will help us investigate on the backend.
I will pass this to the team. Your report helps us prioritize this.
Already deleted the conversation from the Chat, but what you are explaining definitely makes sense. It seems aligned with the behaviour I encountered.
Would loved to still be able use Composer for this use-case too. It is of course not as intelligent as Opus, Sonnet or GPT, but the extra speed really helps stay focus on the work, compared to the other ones.