Hello,
I was using Firecrawl’s MCP through Codex and noticed that the agent attempted to submit feedback three times. All three calls failed with the same error.
Tool call
{
"endpoint": "search",
"jobId": "019f8a0a-a559-709b-b4b1-cb76efe17797",
"rating": "bad",
"issues": ["no_results"],
"note": "No useful results for batch scrape pricing query."
}
Response
[
{
"type": "text",
"text": "{\"success\":false,\"status\":400,\"feedbackErrorCode\":\"INVALID_BODY\",\"error\":\"Invalid request body\",\"retryable\":false}"
}
]
Observations
- The agent used
firecrawl_feedback instead of firecrawl_search_feedback, even though the tool description recommends using the search-specific feedback tool.
- The error response only says
INVALID_BODY, without indicating which field or value was invalid. This makes it difficult for the agent to correct the request.
Hello,
I was using Firecrawl’s MCP through Codex and noticed that the agent attempted to submit feedback three times. All three calls failed with the same error.
Tool call
{ "endpoint": "search", "jobId": "019f8a0a-a559-709b-b4b1-cb76efe17797", "rating": "bad", "issues": ["no_results"], "note": "No useful results for batch scrape pricing query." }Response
[ { "type": "text", "text": "{\"success\":false,\"status\":400,\"feedbackErrorCode\":\"INVALID_BODY\",\"error\":\"Invalid request body\",\"retryable\":false}" } ]Observations
firecrawl_feedbackinstead offirecrawl_search_feedback, even though the tool description recommends using the search-specific feedback tool.INVALID_BODY, without indicating which field or value was invalid. This makes it difficult for the agent to correct the request.