After calling the mcp tool in the responses API, it’s only possible to access the output field of the tool’s result — the API doesn’t return the structuredContent and _meta fields even if the mcp server includes them in its response.
It’s important for me to access the content of these fields in order to implement further client-side logic based on their data. Right now, I have to come up with additional workarounds to pass these fields to the client.
I’m not considering the option of passing JSON-stringified content directly in the output field, because the model will use that payload to generate the final response, which would unnecessarily consume tokens.
