Reading a PDF now returns the document itself plus one image per page.
What's wrong with this entry?
Reading a PDF now returns the actual file as a base64 document block, and page extraction returns one image block per page instead of a summary line. A page that fails to render falls back to a placeholder for that page only.
- The document block is
{ type: "document", source: { type: "base64", media_type: "application/pdf" } }, included only when base64 data is present. - A failed page yields text saying it "could not be processed as an image"; the other pages still come back.
- Re-reading the same file path carries base64 data and already-extracted pages forward from the previous result.
- Page ranges are validated up front: formats like
1-5,3or10-20are accepted, and a range exceeding the per-request page maximum is rejected.
could not be processed as an image
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Read separates the file it opens from the file it reports
Both mention file tool
-
v2.1.246
Write results say when content was replaced without showing a diff
Both mention file tool
-
v2.1.246
Write skips the diff for very large files
Both mention file tool