[waleedlatif1]

Summary

• The Gmail provider card says a search result shows only the opening of its message, not a passage around the match, so a client reads the message before concluding what the rest says. Gmail search returns only a message's opening snippet, while the search tool describes results as carrying "a passage around their match", so clients treated a cut-off snippet as the relevant passage and answered without reading

Type of Change

• Improvement

Testing

• MCP client bench (Sonnet 5.5, 83 cases, 4 attempts per case per arm, paired against this branch's base): a question whose answer sits past the snippet went from 0/4 to 2/4 correct (both correct attempts read the message); correct +0.3pp, completeness, sourceRecall and citedGold flat (every CI spans 0), no case flipped from mostly right to never right, Gmail reads per attempt 0.56 → 0.57, input tokens −3.6%
• bunx vitest run lib/sim-search/live lib/knowledge/mcp on the change (160 passed); no test pins the card text

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Nov 9, 2026 6:02am UTC

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[Low impact] This change appears safe to merge.

Summary

Clarifies that Gmail search results show only a message’s opening, not text around the match.

• Gmail guidance tells clients to read beyond the search result opening.

_{Reviews (1) · Last reviewed commit: "improvement(search): tell clients a Gmai..." · Reviewed by Greptile}