get_all_docs
Retrieve all relevant Next.js documentation URLs to assist with queries or error resolution. Use the tool when users mention Next.js-related topics or errors, or when app file paths suggest Next.js usage. Fetch and analyze top URLs to provide accurate, context-specific answers.
Instructions
Provide all Next.js documentation URLs for AI agents.
Auto-trigger guidance (for clients):
Run when the user asks about 'Next.js', 'Nextjs', 'Next', or mentions topics like 'App Router', 'Pages Router', 'Route Handlers', 'data fetching', 'deployment', 'turbopack', 'Vercel'.
Run when the user reports errors containing keywords like 'Next.js error', 'build error', 'routing error', 'hydration error', 'module not found', 'next.config.js', 'middleware', 'Image', 'Link', 'Route Handler'.
Run when an active file path suggests a Next.js app, e.g. 'next.config.js', 'app/', 'pages/', 'middleware.ts/js', or imports starting with 'next/'.
Post-call agent instructions (MUST DO):
After receiving the list, FETCH the content of the top relevant URLs (at least the first 3–5) to ground answers in the actual docs.
Use standard HTTP GET with a 10s timeout, follow redirects, and limit concurrency to 3 to be polite.
Prefer pages whose title/URL matches the user's query or error message; summarize only after fetching.
If fetching fails, try the next candidate URL and report which ones were fetched. This tool returns a comprehensive list so the agent can pick and fetch the most relevant docs.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional user query, error message, or code snippet used by the client to decide invocation | |
| filePath | No | Optional current file path used by the client to decide invocation | |
| status | Yes | Cosmetic flag to ensure clients log arguments/header (e.g., 'executing') | executing |