fix(web-search-advanced): make text content opt-in, default to highlights

[malob]

Summary

• The web_search_advanced_exa tool unconditionally set contents.text = true in every Exa search request, so every result included full page text. The only way to suppress it was textMaxCharacters: 1, which still returned a 1-character text field on each result — token-wasteful and an awkward escape hatch.
• This was inconsistent with two things:
  • The sibling web_search_exa tool, which sends contents: { highlights: true } and has no text knob.
  • Exa's own Contents Best Practices guide: "Use highlights for agentic workflows: When building multi-step agents that make repeated content extraction calls, highlights provide the most relevant excerpts without flooding context windows."
• After this change, web_search_advanced_exa follows the same default as web_search_exa — highlights only — and full text becomes an explicit opt-in via a new enableText parameter (parallel to the existing enableSummary and enableHighlights).

Changes

• Add enableText: boolean parameter. Off by default.
• Remove the unconditional text: true from the contents block. Text is only requested when enableText is set.
• When no content mode is requested, default contents.highlights = true. This matches web_search_exa and Exa's published guidance for agent workflows.
• Update the textMaxCharacters description to note it requires enableText: true — consistent with how summaryQuery requires enableSummary and highlightsMaxCharacters requires enableHighlights (both siblings already silent-drop without their parent flag).
• Widen ExaAdvancedSearchRequest.contents.highlights to {...} | boolean to allow true as the new default. The API supports this; the sibling ExaSearchRequest.contents.highlights type already allowed it.

Behavior change

This is a behavior change for existing callers of web_search_advanced_exa:

• Before: every search returned full page text by default.
• After: returns highlights only by default. Set enableText: true to restore the old behavior.

web_search_advanced_exa is enabled: false in the default tool registry (src/mcp-handler.ts), so only callers who have explicitly enabled the tool are affected.

Test plan

• npm run ci — typecheck clean, 83 tests passing.
• New file tests/unit/tools/webSearchAdvanced.test.ts covers:
  • Default call (just query) → contents: { livecrawl: "fallback", highlights: true }, no text field.
  • enableText: true → contents: { livecrawl: "fallback", text: true }, no implicit highlights.

[vercel]

@malob is attempting to deploy a commit to the Exa Team on Vercel.

A member of the Team first needs to authorize it.

[malob]

@kesku gentle ping.