`brave_image_search`: should the params support disabling image fetch?

[slimslenderslacks]

Users migrating from having built their own brave image search tools are noting that this version returns the urls in one of the Content blocks, but also returns image Content blocks. Since these content blocks are so large, we're wondering if this is the correct default. We could use tool params to request image content be included/excluded from the CallToolResults.

[jonathansampson]

Users migrating from having built their own brave image search tools are noting that this version returns the urls in one of the Content blocks, but also returns image Content blocks. Since these content blocks are so large, we're wondering if this is the correct default. We could use tool params to request image content be included/excluded from the CallToolResults.

I did intentionally return both image blocks and text blocks (with URLs). That said, it is understandably heavy. What would you prefer to see as the default behavior, as well as configurable alternatives? Thank you for the feedback!

[slimslenderslacks]

I was expecting that the default would be closer to the api response type of https://api.search.brave.com/res/v1/images/search. Since an agent can use those urls to fetch the data if needed, it would make sense that fetching the actual content would be either an additional step, or possibly a non-default option.

[jonathansampson]

@slimslenderslacks, agreed! I'll get that change landed ASAP.