Skip to content

docs: link Alexandria from the Search, Scrape, MCP, CLI, SDK and error pages - #1504

Merged
micahstairs merged 1 commit into
mainfrom
docs/alexandria-cross-page-mentions
Oct 3, 2026
Merged

micahstairs merged 1 commit into
mainfrom
docs/alexandria-cross-page-mentions

Conversation

@claude

@claude claude Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Requested by Micah Stairs · Slack thread

Before: Only the Alexandria page told readers about Alexandria. The Search, Scrape, MCP tools, CLI, SDK and Errors pages did not mention it. A reader on those pages could not find firecrawl_find_tools, the alexandria search source, the alexandria scrape body, or the terms error.

After: Each main page now has a short Alexandria row or section that links to /features/alexandria. Readers can see how to find tools, how to run a tool, and what to do when a provider needs accepted terms. The Alexandria page still holds the detail.

How: I checked each statement against the current API, SDK, MCP server and CLI source. Pages changed:

  • features/search.mdx: alexandria in the sources list, plus an "Alexandria tools" section (data.tools, toolDetail, domainTools, free discovery, a cURL example).
  • features/scrape.mdx: an "Alexandria data tools" section on the alexandria: {provider, capability, options} body, with Python, Node and cURL tabs. It also covers per-item errors, up to 10 calls, creditsCost, x-request-id retries and domainTools on URL scrapes.
  • mcp-server/tools.mdx: a "Choose a tool" row for firecrawl_find_tools and firecrawl_scrape with alexandria, a "Use Alexandria data tools" accordion (discover, inspect, run, terms), and an Alexandria feature card.
  • sdks/cli.mdx: scrape options (--alexandria, --options, --request-id, --domain-tools), search options (alexandria source and its default, --domain-tools, --no-domain-tools, --tool-detail), and an Alexandria section (search alexandria, alexandria list, find-tools, the scrape provider/capability short form, alexandria terms show/accept, alexandria feedback).
  • sdks/node.mdx, sdks/python.mdx, sdks/go.mdx, sdks/rust.mdx: findTools / find_tools / FindTools, and running a tool with scrape / scrape_alexandria / ScrapeAlexandria. All four released SDKs have these methods.
  • api-reference/errors.mdx: a 403 THIRD_PARTY_DATA_TERMS_REQUIRED row. It says to send requiresAction.url to an org admin, and that agents must not accept terms on their own.

I did not change localized files, the features/alexandria.mdx frontmatter, or api-reference/v2-openapi.json. The check-locale-api-literals.sh and check-extraction-hostile-markdown.sh checks give the same output as on main. mint broken-links reports no broken links in the changed pages.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LKCJJgeohVR5dnd1MDBzAR


Generated by Claude Code

…r pages

Add short Alexandria sections that link to /features/alexandria:
- Search: alexandria source, data.tools, toolDetail and domainTools
- Scrape: alexandria body with a code example, results and retries
- MCP tools: firecrawl_find_tools row and an Alexandria workflow
- CLI: scrape and search options, find-tools, list, terms show/accept
- Node, Python, Go and Rust SDKs: find tools and run a tool
- Errors: THIRD_PARTY_DATA_TERMS_REQUIRED (403, requiresAction.url)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LKCJJgeohVR5dnd1MDBzAR
@mintlify

mintlify Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
firecrawl 🟢 Ready View Preview Oct 2, 2026, 2:14 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@claude

claude Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor Author

CI status for this PR

  • Locale literals and extraction-hostile markdown fails at the step "Keep API literals untranslated" (scripts/check-locale-api-literals.sh). This failure is already on main. I ran the script on main at d8ab99e and on this branch. Both runs give the same 14 findings. The findings come from localized pages, probably from the locadex translations in docs(locadex): update translations on main #1500. Examples:

    • es/features/change-tracking.mdx:44 uses seguimientoDeCambios
    • es/webhooks/events.mdx:67 uses rastreo.iniciado
    • pt-BR/v0/sdks/node.mdx:66 uses dadosRaspados

    The later steps were skipped because this step failed. I ran scripts/check-extraction-hostile-markdown.sh on this branch and it passes, the same as on main.

  • Mintlify Validation (firecrawl) - link-rot is neutral, not failing. It reports 202 broken links. A local mint broken-links run shows none of them in the pages that this PR changes.

  • Mintlify Deployment passes.

  • CI does not run scripts/check-hosted-mcp-docs.sh. It fails on main with expected mcp-server.mdx to contain: ## Add an API key, and it fails the same way on this branch. This PR keeps all the text that the script requires in mcp-server/tools.mdx.

This PR changes only English source files and adds no new findings. CLAUDE.md gives localized files to the translation pipeline, so this PR does not edit them.


Generated by Claude Code

@micahstairs
micahstairs marked this pull request as ready for review October 3, 2026 00:33
@micahstairs
micahstairs merged commit b917527 into main Oct 3, 2026
2 of 3 checks passed

This branch was successfully deployed

1 active deployment
staging — 78828ca7 Deployed Oct 2, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants