https://linen.dev logo
Clarification on Action Metadata vs Actual Runtime...
# 🖥│support-forum
j
Hi Team, I’m integrating with the Composio API and I’ve observed a gap between the action metadata returned from /api/v3/tools/{slug} and the actual runtime response returned when executing a tool. Example: OUTLOOK_OUTLOOK_GET_MESSAGE Metadata (via GET /api/v3/tools/OUTLOOK_OUTLOOK_GET_MESSAGE): "output_parameters": { "properties": { "data": { "description": "Data from the action execution", "properties": { "response_data": { "description": "Dictionary with detailed properties of the retrieved email, including sender, recipients, subject, and body, from the Microsoft Graph API.", "type": "object" } }, "type": "object" }, "successful": { "type": "boolean" }, "error": { "type": "string" } } } From metadata, the response_data field is described only as a generic object. Actual execution (via POST /api/v3/tools/execute/OUTLOOK_OUTLOOK_GET_MESSAGE): curl -X POST https://backend.composio.dev/api/v3/tools/execute/OUTLOOK_OUTLOOK_GET_MESSAGE \ -H "x-api-key: API_KEY" \ -H "Content-Type: application/json" \ -d '{ "user_id": "me", "arguments": { "message_id": "..." }, "connected_account_id": "ca_-sOCORHUdPOO" }' Response: { "data": { "response_data": { "id": "AQMkADAwATM0MDAAMi05NTUAOC0yZTU5LTAwAi0wMAoARgAAA8Y...", "subject": "test mail this is subject", "bodyPreview": "test mail this is body", "from": { "emailAddress": { "address": "aiprocess.dev@outlook.com" } }, "toRecipients": [ { "emailAddress": { "address": "aiprocess.dev@outlook.com" } } ], "sentDateTime": "2025-08-22T11:47:27Z", "receivedDateTime": "2025-08-22T11:47:35Z" ... } }, "successful": true, "error": null }
Here, the response_data contains a fully defined structure from Microsoft Graph API (id, subject, bodyPreview, from, toRecipients, timestamps, etc.). My Question Is there a way to obtain a more detailed schema (with expected fields like subject, bodyPreview, from, toRecipients, etc.) from the tools/actions metadata endpoint instead of just a generic object type? Or is the recommended approach to always inspect runtime responses to know the actual field structure for tools?
3 Views