[waleedlatif1]

Summary

• When a batched read_document returns an error entry for a document (a stale or altered ID, a scope change, a provider failure), the server now logs the caller-facing reason at info level
• Before, only unexpected failures were logged, so a batched call that returned errors for every document looked like a success in the logs
• Follow-up to improvement(search-mcp): log rejected tool-call fields and batched read errors #10003, which merged before this commit landed on its branch

Type of Change

• Improvement

Testing

• server.test.ts and server.protocol.test.ts pass; biome clean

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 13, 2026 9:09pm UTC

[greptile-apps]

Confidence Score: 5/5

[Low impact] This PR appears safe to merge.

Summary

Adds an info-level log when a batched read_document returns a known error for a document.

• Batched reads now log each caller-facing document error.

_{Reviews (1) · Last reviewed commit: "improvement(search-mcp): log why a batch..." · Reviewed by Greptile}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}