You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Models tend to encode images as base64 themselves instead of passing file
paths. Make the schema descriptions and tool docs explicit: prefer imageUrl
with a file path, no data: URIs, don't encode images yourself.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
• stamp: x, y, label (any text, e.g. APPROVED, DRAFT, CONFIDENTIAL), color?, rotation?
1813
-
• image: imageUrl or imageData (base64 PNG/JPEG), x?, y?, width?, height?, mimeType?, rotation?, aspect? — places an image (signature, logo, etc.) on the page. imageUrl can be a local file path or HTTP(S) URL; the server fetches and embeds it automatically. Width/height auto-detected from image if omitted.
1820
+
• image: imageUrl or imageData, x?, y?, width?, height?, mimeType?, rotation?, aspect? — places an image (signature, logo, etc.) on the page. imageUrl accepts a local file path or HTTPS URL (NO data: URIs). Do NOT base64-encode images yourself — just pass the file path via imageUrl and the server fetches and embeds it. Width/height auto-detected if omitted.
1814
1821
1815
1822
TIP: For text annotations, prefer highlight_text (auto-finds text) over manual rects.
0 commit comments