docs(scrape): disclose maxAge freshness/speed tradeoff and liveness limits#321
Open
hmishra2250 wants to merge 2 commits into
Open
docs(scrape): disclose maxAge freshness/speed tradeoff and liveness limits#321hmishra2250 wants to merge 2 commits into
hmishra2250 wants to merge 2 commits into
Conversation
…imits
The firecrawl_scrape description sold cache speed ("500% faster") without
disclosing the freshness tradeoff or how to bypass the index, and the maxAge
param had no describe(). This adds a Freshness-vs-speed line, a Liveness line
(a successful render does not prove a listed item is still active), describe()
text on maxAge in both scrapeParamsSchema and parseOptionParamsSchema, and one
reinforcing sentence in the server instructions.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
hmishra2250
force-pushed
the
feat/freshness-maxage-descriptions
branch
from
July 20, 2026 09:59
e78ca75 to
306b2f6
Compare
hmishra2250
marked this pull request as ready for review
July 20, 2026 10:01
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
1 participant
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
The MCP scrape tool mentioned the speed benefit of
maxAge, but did not explain the freshness tradeoff or how to bypass index reuse. Agents also need to know that a successful page response does not by itself prove that the state represented by the page is current.What changed
maxAgein the scrape and parse schemas.maxAge: 0when freshness matters and to inspect source-specific evidence before making a current-state decision.This changes tool descriptions and schema metadata only; runtime behavior is unchanged. Shipping the copy still requires the normal npm publish and hosted MCP redeploy.
Related: firecrawl/skills#5, firecrawl/firecrawl-docs#1145, firecrawl/firecrawl#4082.
Validation
npm run lintnpm test— 9/9 passing