Read a drop's content
dropthis_get_contentRead the exact content a deployed drop serves: fetch the file manifest or one file's text (paged if large) or binary summary by drop ID, optionally from a historical deployment — the read step before editing.
Instructions
Read back the content an EXISTING drop is serving — the content read half of the edit loop: in a read-modify-write / read-before-patch cycle, read with this tool, modify, then ship the new version with dropthis_update_content. Requires drop_id (the drop_… id, id-only; for a public URL or slug call dropthis_resolve first to get the id). By default returns the CURRENT deployment's file manifest (entry plus each file's path, MIME type, and size in bytes); pass deployment_id (from dropthis_list_deployments) to read a historical version — to actually roll a drop back to a prior version, use dropthis_restore_deployment (this tool only reads) — or path (one of the manifest's files[].path values) to fetch one file: text content is returned directly — in the result text and, when it fits, mirrored into structuredContent.content (a file past ~80,000 characters comes back one window at a time, truncated with truncated: true and the next start_char offset — page through the whole file with start_char; never edit a partial window); binary files as a byte-count summary. Use when the user wants to read, view, inspect, diff, or edit what a drop currently serves. NOT for fetching arbitrary web pages (publish with source_url does that), and it returns content only — for a drop's settings/metadata use its read sibling dropthis_get (the two read halves: dropthis_get_content = served content, dropthis_get = settings/metadata).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Fetch this one file's stored content instead of the manifest — one of the manifest's files[].path values, e.g. index.html. | |
| drop_id | Yes | The `drop_…` id of the drop to read (id-only — a URL or slug is rejected; call dropthis_resolve to turn a public URL/slug into its id first). | |
| start_char | No | With `path`: read the text file starting at this character offset (default 0). A file larger than the ~80,000-character window comes back one window at a time — read from 0, then re-call with the `next_start_char` the previous window reported, until it stops. Owner read-back, so this works for historical deployments and password-protected drops that the public URL can't serve. | |
| deployment_id | No | Read this historical deployment (a `dep_…` id from dropthis_list_deployments) instead of the current one. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| next | No | ||
| path | No | ||
| entry | No | ||
| files | No | Manifest: each file's path, contentType, sizeBytes. | |
| binary | No | ||
| dropId | No | ||
| status | No | ||
| content | No | The file's text body, inlined when reading a single text file that fits the cap. | |
| revision | No | ||
| sizeBytes | No | ||
| startChar | No | Character offset this window started at (present when reading past the start). | |
| truncated | No | ||
| contentType | No | ||
| deploymentId | No | ||
| nextStartChar | No | Offset to pass as `start_char` on the next dropthis_get_content call to read the following window; absent at end of file. | |
| returnedChars | No |