feat: add maxCharacters param for highlights, deprecate numSentences/highlightsPerUrl #128
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…highlightsPerUrl Co-Authored-By: [email protected] <[email protected]>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds the new
highlightsMaxCharactersparameter to theweb_search_advanced_exatool and marks the legacyhighlightsNumSentencesandhighlightsPerUrlparameters as deprecated. This aligns the MCP server with the updated Exa API highlights configuration.Changes:
maxCharacters?: numberto the highlights interface intypes.tshighlightsMaxCharactersparameter to the webSearchAdvanced tool schemahighlightsNumSentencesandhighlightsPerUrlto indicate deprecationReview & Testing Checklist for Human
maxCharactersfield name matches the Exa API spec exactlyweb_search_advanced_exatool withhighlightsMaxCharactersparameter to confirm it's passed correctly to the APIhighlightsNumSentences,highlightsPerUrl) still work for backward compatibilityNotes
This is part of a coordinated update across multiple repos (docs, exa-py, exa-js, exa-mcp-server) to add the new
maxCharactershighlights parameter.Link to Devin run: https://app.devin.ai/sessions/f82de373837142da8261ab1462c223eb
Requested by: @LiamHz