Repository navigation
SDK: no-match search returns no libraries; Source Reputation label; clean tool errors - #3299
Merged
Merged
Conversation
enesgules
added a commit
that referenced
this pull request
Oct 1, 2026
…n nothing matches
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
|
Docs7 for context7.com
Commit |
enesgules
added a commit
that referenced
this pull request
Oct 1, 2026
…e (code changes in #3299 and docs7)
enesgules
changed the title
context7
Bot
temporarily deployed
to
Docs7 Preview: fix/ai-sdk-tool-output
October 1, 2026 13:35
Destroyed
ramazanoacar
added a commit
that referenced
this pull request
Nov 11, 2026
* docs: usage metrics reset each calendar month on every plan * docs: fix factual errors in Docs7 docs * docs: correct security pages against current code * docs: fix factual errors in client, SDK and tool docs * docs: recommend an API key instead of anonymous usage * docs: fix factual errors in the Enterprise on-premise docs * docs: fix factual errors in core how-to pages * docs: fix admin button image alt text * docs: remove internal details from verification, refresh, analytics, file types and privacy pages * docs: remove details that do not help readers * docs: keep the AI SDK tool output examples; the code now matches them (#3299) * docs: keep the SDK no-match example and drop the hex-only callout note (code changes in #3299 and docs7) * docs: remove the anonymous-usage line from the Pi page * docs: recommend an API key in two client setups added on master * docs: link the subprocessor list and keep the API key storage note short * docs: use live React library IDs and state the CLI Node.js requirement /facebook/react and /facebook/react-native now return library_redirected, so every example that used them printed a redirect notice and no docs. Examples now use /reactjs/react.dev (the first search result for React), /react/react-native, and /react/react/v19.2.8 for the versioned example. The ctx7 CLI needs Node.js 22.13 or later (commander 15 needs 22.12+, @InQuirer needs 22.13+ on the 22 line), not Node.js 18. * docs: link the ChatGPT Developer Mode help article The developers.openai.com Developer Mode guide now returns 404. --------- Co-authored-by: Ramazan Onur Acar <ramazanonuracar@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
context7
Bot
temporarily deployed
to
Docs7 Preview: fix/ai-sdk-tool-output
November 11, 2026 13:08
Destroyed
ramazanoacar
approved these changes
Nov 11, 2026
ramazanoacar
left a comment
ramazanoacar
left a comment
Contributor
There was a problem hiding this comment.
Checked against master: the API answers 404 on /v2/libs/search only when nothing matches, so returning an empty list is right. The label now matches the MCP server, and the tool messages lose the misleading API key hint. CI passes on current master.
This branch was successfully deployed
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
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.
Why
Context7Error, so every caller needed a try/catch for the normal "nothing found" case. The AI SDK tool also passed that error through asError searching for libraries: No libraries found for "x". Try a different search term.. Check your API key and try again.That text has a double period and a wrong hint.Trust Score. The MCP server and the tool prompts say "Source Reputation".What
@upstash/context7-sdk(minor):searchLibraryreturns[]on a 404 from the API. Withtype: "txt", it returns "No libraries found matching your query. Try a different search term or check the library name."- Source Reputation: High|Medium|Low|Unknown.getContextandsearchstill throw on 404, because an unknown library ID is a real error that the caller must fix.@upstash/context7-tools-ai-sdk(patch):resolveLibraryIdreturns the SDK result as it is.queryDocsturns a 404 into its "No documentation found … use resolveLibraryId" hint.resolveLibraryIdno-match example uses the new message. The SDKsearchLibraryexample on master already checkslibraries.length === 0, which now works.Checks
OPENROUTER_API_KEY, and they fail without it, with or without this change.Next.jsgivesSource Reputation: High./invalid/librarygives the "No documentation found" hint.