Skip to content
English
Go to merchantspring.io
  • There are no suggestions because the search field is empty.

How do I troubleshoot an unexpected MerchantSpring MCP result?

Use this checklist when the AI response does not match the MerchantSpring data or analysis you expected.

An unexpected MCP result can be caused by an ambiguous prompt, an incorrect tool or parameter, stale connector instructions, data availability or the AI application's interpretation of the response.

Troubleshooting steps
  1. Confirm the account, channels, marketplaces and countries included
  2. Check the date range, interval, filters and comparison period
  3. Review any assumptions made by the AI application
  4. Confirm the MerchantSpring connector and tool were used
  5. Refresh the MerchantSpring tool list or reconnect the connector
  6. Retry with a more precise prompt
  7. Narrow or split the request if the report is very large
Why can large reports cause problems?

A large CSV, long date range or high number of channels can exceed the AI application's practical file or context limits even when MerchantSpring generated the report successfully.

What should I send to Support?
  • Your MerchantSpring user email and account/company
  • The AI application and connector used
  • The exact prompt and expected result
  • The actual output or displayed error
  • A conversation share or session ID
  • The approximate date, time and timezone
  • Whether you refreshed or reconnected the tools
Security reminder

Do not include your full MerchantSpring API key in the conversation, screenshots or support request.

Need more help? Contact MerchantSpring Support at support@merchantspring.io.