Trying to fetch products through Catalog MCP and got this:
{
“jsonrpc”: “2.0”,
“id”: 1,
“method”: “tools/call”,
“params”: {
“name”: “search_global_products”,
“arguments”: {
“query”: “wedding dress”,
“context”: “buyer wants nice clothes”,
“limit”: 300,
“min_price”: 20.0,
“max_price”: 2000.0,
“available_for_sale”: true,
“shop_ids”: [
“59897544862”
]
}
}
}
Catalog MCP returned an error:
{
“code”: -32603,
“message”: “Internal error”,
“data”: “Invalid arguments: The property ‘#/limit’ did not have a maximum value of 10, inclusively in schema 90746ae2-6d86-5aeb-9c12-a94b348dfec2”
}
I am also seeing this. 10 does not help us at all.
Hi @Ramon_Medeiros and @Jake_Boyles,
I’ve looked into this a bit and was able to replicate this on my own app as well, and after further investigation internally, I can confirm that 10 is actually the expected maximum value usable with the limit argument of the search_global_products tool.
In this case, it’s the Catalog MCP documentation that is incorrect here, though the Catalog REST API documentation does actually mention the correct limit values.
At this time I’ve reached out to our team internally to have the Catalog MCP documentation updated with the correct values as well.
I do understand this limit is not ideal for your use cases, and I absolutely will be sharing some feedback internally that you’d like to see a higher limit value for these MCP requests. While we can’t guarantee when or if this will be increased, I can assure you that our developers and product managers do take all of our partner and merchant feedback into great value when determining future features and platform changes.
To help ensure the most accurate feedback is passed on, can you share some details on your exact use case and why a limit of 10 is restricting your use case?
We’re using it for finding clothes and shoes. Sizing is still very much off so we have to post filter. For example if I say size 2 nike shoes. I get bac size 23, 2Y etc. So that 10 quickly becomes 1-3 at most. If it was 100 we could live with having to red rid of half the results.
Similar case here. 100 would be an interesting limit
@Jake_Boyles and @Ramon_Medeiros,
Thank you for the additional context, I’ll pass this on to our development team internally, though as mentioned we can’t guarantee if this change will be implemented. I’d recommend keeping an eye on our Shopify.dev changelog just in case.
Is there a better way to search for sizes? I just put it in the query now but 95% of the time it doesnt match. For shoes and clothes we say girls or boys or mens or womens and that gets us close but then we only want to show clothes that match the users sizes.
Hi @Jake_Boyles,
Great question. The short answer is that the Catalog MCP doesn’t currently support structured variant-level filtering (like size or color) at the search level.
It’s easy to see why you’re asking about this and currently, there isn’t a great workaround to use here. We’re aware of this gap and actively working on a resolution that will bring structured attribute filtering (including size) to the Catalog API search. I’d recommend keeping an eye on the Shopify.dev changelog for updates as we don’t have a specific timeline on this currently.
I hope this helps and please let us know if you have any other questions.