When to use: You hit a paywall-free article, docs page, or blog post and want TL;DR plus an opinion without reading it yourself.
Flow
-
Fetch with Markdown output
Fetch https://example.com/blog/post and give me the first ~3000 chars as clean Markdown.✓ Copied
→ Content arrives with working headings and no nav chrome
-
Summarize and extract claims
Summarize in 5 bullets. List any specific numbers or claims the author makes, with the sentence they appear in.✓ Copied
→ Bulleted summary plus cited quotes, not paraphrased
-
Critique
What's the strongest counter-argument to the author's main thesis? Be specific.✓ Copied
→ Real critique, not 'on the other hand...' mush
Outcome: A useful read of the article in 30 seconds, with quotes you can verify.
Pitfalls
- Page is JS-rendered and fetch returns a near-empty shell — Check first fetch output — if it's suspiciously short or says 'Loading...', switch to Firecrawl or Chrome DevTools MCP
- Long page truncated by max_length — Use
start_index to paginate: second call with start_index: 5000 picks up where the first left off
When to use: A library you depend on publishes release notes on a static page and you haven't checked in a month.
Flow
-
Fetch the changelog page
Fetch https://vendor.com/changelog and list every release since 2026-03-01 with its date and a one-line summary of what changed.✓ Copied
→ Chronological list with dates
-
Classify by impact
Categorize each into: breaking change, new feature, bug fix, internal. Flag anything marked breaking or deprecated.✓ Copied
→ Per-release tag with breaking items called out
-
Call out what affects us
We use this library mainly for <feature X>. Which of these changes affect our usage, and what action (if any) should we take?✓ Copied
→ Actionable list, not generic 'review the notes'
Outcome: Know in 2 minutes whether you need to bump the version and test, or skip the release entirely.
Pitfalls
- Changelogs paginate — first page only has last 2 months — Scroll with
start_index or fetch the archive URL explicitly - GitHub release pages render via JS now — Use the raw API instead:
https://api.github.com/repos/owner/repo/releases returns JSON without needing JS
When to use: You're coding against a public spec (OAuth, RFC 9457 problem details, a REST API's reference docs) and want Claude to have the canonical source.
Flow
-
Fetch the spec page(s)
Fetch https://datatracker.ietf.org/doc/html/rfc9457 as Markdown. Return just sections 1-4.✓ Copied
→ Clean Markdown of the normative sections
-
Implement against it
Using that RFC as the source of truth, write me a TypeScript type plus validator for the problem details object. Cite specific section numbers in comments.✓ Copied
→ Code with inline // per RFC 9457 §3.1 references
-
Edge case check
From the same RFC, what edge cases or optional fields does my implementation not handle? Decide whether to handle them or document the choice.✓ Copied
→ Honest gap analysis against the spec
Outcome: A spec-faithful implementation with traceable citations you can defend in code review.
Pitfalls
- IETF pages are huge — a whole RFC can exceed context budget — Fetch only the sections you need using anchor links or start_index, not the full doc