# Required ship date returning error

**URL:** <https://community.shiphero.com/t/required-ship-date-returning-error/3761>\
**Category:** GraphQL API\
**Created:** [August 11, 2026, 6:50pm UTC](https://community.shiphero.com/t/required-ship-date-returning-error/3761 "2026-08-11T18:50:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lflaerty](https://avatars.discourse-cdn.com/v4/letter/l/7ba0ec/32.png) [@lflaerty](https://community.shiphero.com/u/lflaerty)\
**Post date:** [August 11, 2026, 6:50pm UTC](https://community.shiphero.com/t/required-ship-date-returning-error/3761/1 "2026-08-11T18:50:58Z")

</div>

Hi folks,

I’m trying to set up a dashboard that will show specific orders that need to be fulfilled within the next week. When I passed `required_ship_date_from` / `required_ship_date_to` as filter arguments to the `orders` query, the MCP tool call itself failed

Error executing tool shiphero\_query\_execute: ShipHero API request failed.

I’m using Claude co-work through the Shiphero MCP.

Any advice appreciated!

---

<div class="post-metadata">

**Author:** ![lpezza](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@lpezza](https://community.shiphero.com/u/lpezza)\
**Post date:** [August 12, 2026, 7:04pm UTC](https://community.shiphero.com/t/required-ship-date-returning-error/3761/2 "2026-08-12T19:04:41Z")

</div>

Hi @lflaerty, i expect you are doing well!

Your query is fine. **required\_ship\_date\_from** and **required\_ship\_date\_to** are both valid arguments on **orders**.

What’s going wrong is timing. The query is taking more than 30 seconds to come back, and 30 seconds is where the MCP server gives up on a request. When that happens you get **ShipHero API request failed** , which unfortunately reads like we rejected your arguments. We didn’t, the call just got cut off while it was still running.

That’s why the MCP isn’t the right tool for what you’re building. It’s meant for quick questions where someone’s sitting there waiting on an answer, so the timeout is short on purpose. A dashboard that scans a week of ship dates is a heavier job, and it’ll keep running into that limit no matter how you write the query.

A good alternative to solve this is our **Public API Skill**. Your agent gets its own token and talks to the GraphQL API directly, so the MCP and its timeout are out of the picture, and the skill already knows how to shape orders queries so they come back fast. Two caveats: it needs a coding agent (Claude Code, Codex or Cursor, not CoWork).

Download and setup: [ShipHero AI Toolkit – Developer Resources | ShipHero](https://developer.shiphero.com/shiphero-ai-toolkit/) .

One last thing:

It would also help if you linked your **ShipHero account ID** to your **Community profile**.

1. Click your profile picture in the top right corner and go to your **Profile**.
2. Select **Preferences**.
3. From the options that appear, click **Profile**.
4. Scroll down until you find the text box for your **ShipHero account ID** , and add it there.

Many thanks! And I hope you find this useful!