https://linen.dev logo
Google cal tools bad requests - generic error mess...
# 🖥│support-forum
r
I'm seeing frequent Bad Request errors when calling the
GOOGLECALENDAR_EVENTS_LIST
tool. It doesn’t appear to be a scope issue, since the call occasionally succeeds. However, when it fails, the logs only show a generic 400 response with the message "Bad Request". Is there a way for me to get more visibility into what's causing the failure (e.g. invalid parameters, bad date formats, etc.)? Thanks
Copy code
json
{
  "extras": null,
  "level": "ERROR",
  "message": "Error executing `EVENTS_LIST`: Traceback (most recent call last):\n  File \"/var/task/mercury/tools/api/tool.py\", line 283, in execute\n    response = instance.execute(request=request, metadata=metadata)\n  File \"/tmp/apps/googlecalendar/actions/events_list.py\", line 210, in execute\n    raise ExecutionFailed(\nmercury.tools._base.exceptions.ExecutionFailed: Failed to list events. Status: 400. Response: {\n  \"error\": {\n    \"errors\": [\n      {\n        \"domain\": \"global\",\n        \"reason\": \"badRequest\",\n        \"message\": \"Bad Request\"\n      }\n    ],\n    \"code\": 400,\n    \"message\": \"Bad Request\"\n  }\n}\n",
  "requestId": "9be96cc4-31e9-4a3c-824c-03229ba0cd8b",
  "time": "2025-08-06T15:43:49.909544+00:00",
  "type": "system"
}
c
Hi Kristen, Could you share your SDK version? Also, let me know if you are using any frawmework.
r
Yup! @composio/core@0.1.40 @composio/vercel@0.1.40 Using the vercel ai sdk@5.0.0-beta.25
c
We just checked it and it seems like there's a bug on our end, I've forwarded it to the engg team. Also, you can get verbose logs by
export COMPOSIO_LOG=debug
in your terminal or in your environment.
r
Thanks for checking. Is there an eta when that tool will be fixed?
c
Let me check with the team and revert with details
r
Hey Uday, any update with this one?
c
Hi kristen, Could you try passing
timeMin
and
timeMax
params while along with the current params? Let me know if that works for you? Google API ref:
r
Those work, but they're not considered required fields so it fails everytime they're not passed in from the llm
a
Yes, we'll push a fix for this, a temporary workaround would to to pass them with value as "". You can use a [before execute](https://docs.composio.dev/docs/modifiers/before-execution) for this.
c
Hey there, I've looked into this issue. Basically, we cannot mark them as required but we pass the default values for these two fields. Ideally, when you execute this manually via SDK, it should still work. Even when an LLM is executing this action and is not passing any values for these two fields, Composio passes the default values for these two fields.
r
Thanks for the response. Just wondering is that a recent update or was that always the behavior?
c
This is the default behaviour and this is how we always handled this case.