Free iMessage, WhatsApp, Instagram DM and Reddit chat videos (1080x1920 MP4) and screenshots.
Scored across 7 tools
Every tool is a distinct resource+action pair: chat, lockscreen, and reddit each split cleanly into render_video, screenshot, and (for chat) validate. The resource prefix and action suffix make it impossible to mistake one for another.
All seven tools follow a uniform {resource}_{action} snake_case pattern (chat_render_video, lockscreen_screenshot, reddit_validate-less but consistent). No mixed conventions or stray verb styles.
Seven tools is well-scoped for three content types times render/screenshot plus one validator. Each tool earns its place with no redundancy.
Core render/screenshot coverage is solid and both render and screenshot paths surface validation errors, but chat gets a dedicated validate tool while lockscreen and reddit do not, and 'uploaded photo's number' is referenced with no upload tool exposed.
Render a txtreel conversation (script or messages) to an MP4 and wait for it to finish. This queues a render, waits for it, and returns once it is done (or after failing/timing out). A short render (a handful of messages) typically takes 20-60 seconds.
Returns a public link to the MP4; the file is deleted after 24 hours. If txtreel is busy or you hit the rate limit, the result is an error with the message.
Conversation script format (one event per line):
them: hey, you up? me: yeah why [pause 1.5] wait 1.5 s --- Today 9:41 PM date/time separator me: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number) [them reacts ❤️] reaction on my last message [read] they read my messages === everything above is already on screen at the start === scroll 3 same, but open on the oldest message and skim down in 3 s
"Name: text" also means "them" when Name matches contact.name (e.g. contact.name "Sam" lets you write "Sam: omg" instead of "them: omg"). A literal "\n" inside a message becomes a line break. Lines starting with # are comments.
Photos: "me: [photo https://example.com/image.jpg] optional caption" (https URLs only; local file paths are not available). "=== scroll 3" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits.
| Name | Required | Description | Default |
|---|---|---|---|
| speed | No | Pacing multiplier; 2 = twice as fast, 0.5 = half speed. Default: 1. | |
| theme | No | Color theme, "light" or "dark". Default: light. | |
| script | No | Conversation as a plain-text script. Use this OR messages, not both. Conversation script format (one event per line): them: hey, you up? me: yeah why [pause 1.5] wait 1.5 s --- Today 9:41 PM date/time separator me: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number) [them reacts ❤️] reaction on my last message [read] they read my messages === everything above is already on screen at the start === scroll 3 same, but open on the oldest message and skim down in 3 s # comment "Name: text" also means "them" when Name matches contact.name (e.g. contact.name "Sam" lets you write "Sam: omg" instead of "them: omg"). A literal "\n" inside a message becomes a line break. Lines starting with # are comments. Photos: "me: [photo https://example.com/image.jpg] optional caption" (https URLs only; local file paths are not available). "=== scroll 3" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits. | |
| sounds | No | Real UI sounds: iOS key clicks while typing, the app's send and receive sounds. Default: true. | |
| contact | No | Contact header info. | |
| endHold | No | Seconds to hold on the final frame before the video ends. Default: 2. | |
| autoRead | No | Mark "me" messages as read as soon as the other person starts typing. Default: true. | |
| keyboard | No | Show the iOS keyboard, which keeps the latest messages above the Reels caption area. Default: true. | |
| messages | No | Conversation as an array of event objects instead of a script string (use this OR script, not both). Passed through to the txtreel API as-is; each item is one of: {from:"me"|"them", text, delay?, typing?, hold?, time?, instant?} (type "message" is the default and can be omitted), {type:"pause", seconds}, {type:"timestamp", text, instant?}, {type:"read", time?}, {type:"react", from:"me"|"them", emoji}. | |
| platform | No | Chat app to render: "imessage", "whatsapp", or "instagram". Default: imessage. | |
| startTime | No | Clock used for messages, read receipts, and WhatsApp bubble times, e.g. "9:41 PM". Default: 9:41 PM. | |
| statusBar | No | Phone status bar shown at the top of the frame. | |
| composerTyping | No | Type "me" messages into the input bar before sending them. Default: true. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only mark it as a non-idempotent, non-destructive, non-open-world write. The description adds substantial behavior the agent cannot get elsewhere: the render is queued and awaited, it returns only on completion/failure/timeout, typical latency is 20-60s, output is a public link whose file is deleted after 24 hours, and rate-limit/busy conditions surface as errors with a message. That is exactly the kind of disclosure annotations do not carry.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose, timing, and return-value caveats are correctly front-loaded in the opening sentences. The bulk of the description is a script-format block that largely duplicates the script parameter's schema description, which is redundant weight rather than new information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 13 parameters (including nested objects) and no output schema, the description appropriately compensates by describing the return value (public MP4 link, deleted after 24h) and failure modes. Parameter-level detail is delegated to a fully covered schema, so an agent has what it needs to call the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description re-explains the script format, but that text is essentially duplicated from the script parameter's own schema description, so it adds little beyond the structured field; the other twelve parameters (speed, theme, platform, statusBar, etc.) get no additional semantic framing in the prose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence gives a concrete verb+resource+output: 'Render a txtreel conversation (script or messages) to an MP4 and wait for it to finish.' That is unambiguous and clearly a video-render tool, implicitly distinct from chat_screenshot. It never names its siblings (chat_screenshot, chat_validate, reddit_render_video), so it stops short of full differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It conveys operational context (queues then waits, 20-60s for a short render, errors on busy/rate limit) and states 'use this OR messages, not both,' which is useful guidance. However it never says when to prefer this over chat_screenshot or chat_validate, nor any when-not conditions, so usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Render a single frame of a txtreel conversation (script or messages) to a PNG and return it as an image. Defaults to the last frame — pass "frame" to capture an earlier moment (30 fps).
Returns the PNG as image content, plus a text line with the PNG's URL (expires after 24 hours).
Conversation script format (one event per line):
them: hey, you up? me: yeah why [pause 1.5] wait 1.5 s --- Today 9:41 PM date/time separator me: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number) [them reacts ❤️] reaction on my last message [read] they read my messages === everything above is already on screen at the start === scroll 3 same, but open on the oldest message and skim down in 3 s
"Name: text" also means "them" when Name matches contact.name (e.g. contact.name "Sam" lets you write "Sam: omg" instead of "them: omg"). A literal "\n" inside a message becomes a line break. Lines starting with # are comments.
Photos: "me: [photo https://example.com/image.jpg] optional caption" (https URLs only; local file paths are not available). "=== scroll 3" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits.
| Name | Required | Description | Default |
|---|---|---|---|
| frame | No | Frame index to capture, at 30 fps (e.g. 30 = one second in). Omit to capture the final frame of the conversation. | |
| speed | No | Pacing multiplier; 2 = twice as fast, 0.5 = half speed. Default: 1. | |
| theme | No | Color theme, "light" or "dark". Default: light. | |
| script | No | Conversation as a plain-text script. Use this OR messages, not both. Conversation script format (one event per line): them: hey, you up? me: yeah why [pause 1.5] wait 1.5 s --- Today 9:41 PM date/time separator me: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number) [them reacts ❤️] reaction on my last message [read] they read my messages === everything above is already on screen at the start === scroll 3 same, but open on the oldest message and skim down in 3 s # comment "Name: text" also means "them" when Name matches contact.name (e.g. contact.name "Sam" lets you write "Sam: omg" instead of "them: omg"). A literal "\n" inside a message becomes a line break. Lines starting with # are comments. Photos: "me: [photo https://example.com/image.jpg] optional caption" (https URLs only; local file paths are not available). "=== scroll 3" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits. | |
| sounds | No | Real UI sounds: iOS key clicks while typing, the app's send and receive sounds. Default: true. | |
| contact | No | Contact header info. | |
| endHold | No | Seconds to hold on the final frame before the video ends. Default: 2. | |
| autoRead | No | Mark "me" messages as read as soon as the other person starts typing. Default: true. | |
| keyboard | No | Show the iOS keyboard, which keeps the latest messages above the Reels caption area. Default: true. | |
| messages | No | Conversation as an array of event objects instead of a script string (use this OR script, not both). Passed through to the txtreel API as-is; each item is one of: {from:"me"|"them", text, delay?, typing?, hold?, time?, instant?} (type "message" is the default and can be omitted), {type:"pause", seconds}, {type:"timestamp", text, instant?}, {type:"read", time?}, {type:"react", from:"me"|"them", emoji}. | |
| platform | No | Chat app to render: "imessage", "whatsapp", or "instagram". Default: imessage. | |
| startTime | No | Clock used for messages, read receipts, and WhatsApp bubble times, e.g. "9:41 PM". Default: 9:41 PM. | |
| statusBar | No | Phone status bar shown at the top of the frame. | |
| composerTyping | No | Type "me" messages into the input bar before sending them. Default: true. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover safety (destructiveHint=false, openWorldHint=false), and the description adds real context beyond them: the concrete return shape (PNG image content plus a text line with a URL) and the 24-hour URL expiry. It omits auth requirements and any rendering cost/rate-limit notes, which would have pushed it higher.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The first sentence front-loads what it does, the frame default, and the return format before any format detail, so a reader can stop early. The remaining bulk is a DSL specification, which is dense but each line earns its place as syntax documentation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 14-parameter, nested-object tool with no output schema, the description admirably covers the script DSL and the return payload. It is still incomplete on the workflow side: no mention of the chat_validate sibling for checking scripts before rendering, and no guidance on script vs messages trade-offs beyond 'not both'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3; every parameter is already documented in the schema. The script-format prose in the description largely duplicates the schema's own 'script' description verbatim, adding little new semantic meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource — 'Render a single frame of a txtreel conversation (script or messages) to a PNG' — and the 'single frame' framing implicitly separates it from chat_render_video without opening either schema. An agent knows immediately this produces a still image, not a video.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explains the frame default and the script-vs-messages mutual exclusion ('use this OR messages, not both'), which is genuine routing guidance. However, it never says when to prefer this over chat_render_video or to run chat_validate first, so sibling selection is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Checks a txtreel conversation (script or messages) without rendering anything. It is fast and free.
On success returns { ok: true, durationSeconds, messageCount, conversation } where "conversation" is the fully-resolved object (all defaults applied). On failure returns { ok: false, errors: string[] } — one message per problem; when the input was a script, errors are prefixed with the offending line number. Videos longer than the server limit are rejected here too.
Conversation script format (one event per line):
them: hey, you up? me: yeah why [pause 1.5] wait 1.5 s --- Today 9:41 PM date/time separator me: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number) [them reacts ❤️] reaction on my last message [read] they read my messages === everything above is already on screen at the start === scroll 3 same, but open on the oldest message and skim down in 3 s
"Name: text" also means "them" when Name matches contact.name (e.g. contact.name "Sam" lets you write "Sam: omg" instead of "them: omg"). A literal "\n" inside a message becomes a line break. Lines starting with # are comments.
Photos: "me: [photo https://example.com/image.jpg] optional caption" (https URLs only; local file paths are not available). "=== scroll 3" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits.
| Name | Required | Description | Default |
|---|---|---|---|
| speed | No | Pacing multiplier; 2 = twice as fast, 0.5 = half speed. Default: 1. | |
| theme | No | Color theme, "light" or "dark". Default: light. | |
| script | No | Conversation as a plain-text script. Use this OR messages, not both. Conversation script format (one event per line): them: hey, you up? me: yeah why [pause 1.5] wait 1.5 s --- Today 9:41 PM date/time separator me: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number) [them reacts ❤️] reaction on my last message [read] they read my messages === everything above is already on screen at the start === scroll 3 same, but open on the oldest message and skim down in 3 s # comment "Name: text" also means "them" when Name matches contact.name (e.g. contact.name "Sam" lets you write "Sam: omg" instead of "them: omg"). A literal "\n" inside a message becomes a line break. Lines starting with # are comments. Photos: "me: [photo https://example.com/image.jpg] optional caption" (https URLs only; local file paths are not available). "=== scroll 3" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits. | |
| sounds | No | Real UI sounds: iOS key clicks while typing, the app's send and receive sounds. Default: true. | |
| contact | No | Contact header info. | |
| endHold | No | Seconds to hold on the final frame before the video ends. Default: 2. | |
| autoRead | No | Mark "me" messages as read as soon as the other person starts typing. Default: true. | |
| keyboard | No | Show the iOS keyboard, which keeps the latest messages above the Reels caption area. Default: true. | |
| messages | No | Conversation as an array of event objects instead of a script string (use this OR script, not both). Passed through to the txtreel API as-is; each item is one of: {from:"me"|"them", text, delay?, typing?, hold?, time?, instant?} (type "message" is the default and can be omitted), {type:"pause", seconds}, {type:"timestamp", text, instant?}, {type:"read", time?}, {type:"react", from:"me"|"them", emoji}. | |
| platform | No | Chat app to render: "imessage", "whatsapp", or "instagram". Default: imessage. | |
| startTime | No | Clock used for messages, read receipts, and WhatsApp bubble times, e.g. "9:41 PM". Default: 9:41 PM. | |
| statusBar | No | Phone status bar shown at the top of the frame. | |
| composerTyping | No | Type "me" messages into the input bar before sending them. Default: true. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, and the description goes further by disclosing both return shapes ({ok:true,...} vs {ok:false, errors[]}), the line-number error prefixing, and server-length rejection. That is substantive behavioral context beyond the annotations, though it omits any note on limits specifics or latency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The return-shape summary is well front-loaded, but the description then duplicates the entire multi-line script format block already present in the script parameter's schema description, which is significant redundancy for a definition of this size.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and 13 mostly-optional parameters, the definition compensates by spelling out success and failure return shapes and error formatting, and it covers the script grammar an agent must produce. Nothing essential for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all 13 parameters, including defaults, enums, and ranges. The description repeats the script format and keyboard behavior verbatim rather than adding meaning beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Checks/validates) and resource (a txtreel conversation, script or messages) and explicitly sets itself apart from rendering siblings with 'without rendering anything'. An agent can distinguish it from chat_render_video and chat_screenshot immediately.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'without rendering anything' and 'It is fast and free' clearly establish the context for using this over the render/screenshot siblings, but it never explicitly says to validate before rendering or names the alternative. Clear usage context, no explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Render an iOS lock screen with notifications to an MP4 and wait for it to finish: a wallpaper, the big clock, and cards from imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders that land one by one at the seconds you set. This queues a render, waits for it, and returns once it is done (or after failing/timing out). A short render (3-5 notifications) typically takes 20-60 seconds.
Returns a public link to the MP4; the file is deleted after 24 hours. If txtreel is busy or you hit the rate limit, the result is an error with the message.
If the input is invalid, this returns an error result with the validation messages instead of rendering.
Lock screen format (an iOS 26 lock screen with notifications):
The video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a see-through time such as "now" or "2m ago". A card lands at its "at" second (seconds from the start of the video), growing out of the bottom of the screen (or out of the card already there) as on iOS 26; at 0 it is already there. While cards are on screen the lower half of the wallpaper darkens, as on the phone. At least one notification is required. The video ends "endHold" seconds (default 2) after the last card has settled.
Wallpaper and avatars are https image URLs or data: URIs (local file paths are not available). "wallpaper" also takes one of Apple's iOS 26 wallpapers by name ("sky", "shadow", "halo", "dusk", "yellow", "pink", "azure", "purple"); without one, "sky" (the iOS 26 default) is drawn, in its light or dark version with "theme". "avatar" on a notification shows the contact's photo with the app icon as a small badge. "display": "stack" folds the cards like iOS 26 does (the newest card, the next one or two as one-line rows under it, the rest counted as "+3 from WhatsApp and Messages"); "list" shows every card.
| Name | Required | Description | Default |
|---|---|---|---|
| dim | No | Black overlay on the wallpaper, 0 to 1. Default: 0. | |
| date | No | The line above the clock, written as iOS 26 does, e.g. "Tue Oct 6". Default: "Tue Oct 6". | |
| time | No | The big clock, without AM/PM, e.g. "9:41". Default: "9:41". | |
| theme | No | The phone's appearance: "light" = frosted glass, "dark" = smoked glass, white text on both as on iOS 26; Apple's wallpapers follow it. Default: light. | |
| camera | No | Camera button bottom right. Default: true. | |
| sounds | No | The iOS notification tone when each card lands (video only). Default: true. | |
| carrier | No | Network name on the left of the status bar. Default: none. | |
| display | No | "list" shows every card, newest on top; "stack" is iOS 26's default fold: the newest card, the next one or two as one-line rows, the rest counted. Default: list. | |
| endHold | No | Seconds to hold on the last frame after the last card has settled. Default: 2. | |
| padlock | No | Small locked padlock above the date. Default: true. | |
| clockSize | No | Clock size in points on a 402 pt wide iPhone screen. Default: 100. | |
| statusBar | No | Right side of the status bar. (The clock there is not shown on a lock screen.) | |
| wallpaper | No | One of Apple's iOS 26 wallpapers by name ("sky", "shadow", "halo", "dusk", "yellow", "pink", "azure", "purple"), or a full-bleed image: URL or data: URI. Omitted: "sky", the iOS 26 default. | |
| clockColor | No | Clock colour (CSS colour). Default: "#FFFFFF". | |
| flashlight | No | Flashlight button bottom left. Default: true. | |
| wallpaperX | No | Where the crop is centred horizontally when the image is not the screen's shape, in % (50 = middle). Default: 50. | |
| wallpaperY | No | Where the crop is centred vertically, in % (50 = middle). Default: 50. | |
| clockWeight | No | Clock numeral weight, 100-900. Default: 760. | |
| clockOpacity | No | How much of the colour fills the Liquid Glass numerals, 0-1; the wallpaper shows through the rest. Default: 0.45. | |
| clockStretch | No | Vertical stretch of the clock numerals. Default: 1.16. | |
| notifications | Yes | The notifications, 1 to 20, in any order (they land in order of "at", ties keep the written order, and the newest sits on top). Lock screen format (an iOS 26 lock screen with notifications): The video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a see-through time such as "now" or "2m ago". A card lands at its "at" second (seconds from the start of the video), growing out of the bottom of the screen (or out of the card already there) as on iOS 26; at 0 it is already there. While cards are on screen the lower half of the wallpaper darkens, as on the phone. At least one notification is required. The video ends "endHold" seconds (default 2) after the last card has settled. Wallpaper and avatars are https image URLs or data: URIs (local file paths are not available). "wallpaper" also takes one of Apple's iOS 26 wallpapers by name ("sky", "shadow", "halo", "dusk", "yellow", "pink", "azure", "purple"); without one, "sky" (the iOS 26 default) is drawn, in its light or dark version with "theme". "avatar" on a notification shows the contact's photo with the app icon as a small badge. "display": "stack" folds the cards like iOS 26 does (the newest card, the next one or two as one-line rows under it, the rest counted as "+3 from WhatsApp and Messages"); "list" shows every card. | |
| wallpaperZoom | No | 1 = cover the screen, 2 = twice as close. Default: 1. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnly=false, idempotent=false), the description discloses the synchronous queue-and-wait behavior, typical runtime, that the result is a public MP4 link deleted after 24 hours, and that rate limiting, busy states, and invalid input produce error results. This is exactly the operational context an agent needs for a long-running render.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The first two sentences are well front-loaded, but the third paragraph restates the lock screen format almost verbatim from the notifications schema description, making the text noticeably redundant for a field already documented at 100% coverage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 22-parameter, nested-schema tool with no output schema, the description covers the return artifact (public MP4 link, 24-hour expiry), timing expectations, and all error classes. An agent can invoke and interpret this call without further information.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: how 'display': 'stack' visually folds cards versus 'list', how avatars badge the app icon, how the landing animation works at each 'at' second, and that wallpaper/avatar only accept URLs or data: URIs (no local paths). These are behavioral semantics not fully conveyed by the parameter docs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening sentence states a specific verb and resource (render an iOS lock screen with notifications to an MP4) and the waiting semantics. It is clearly distinguishable from siblings like lockscreen_screenshot and chat_render_video, which produce different artifacts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear operational context: it queues a render, blocks until finished, and returns or fails on timeout. It also lists failure conditions (busy, rate limit, invalid input) and realistic duration (20-60s). It does not, however, explicitly route the agent away from sibling tools such as lockscreen_screenshot.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Render a single frame of an iOS lock screen with notifications to a PNG and return it as an image. Defaults to the last frame — pass "frame" to capture an earlier moment (30 fps).
Returns the PNG as image content, plus a text line with the PNG's URL (expires after 24 hours).
If the input is invalid, this returns an error result with the validation messages instead of an image.
Lock screen format (an iOS 26 lock screen with notifications):
The video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a see-through time such as "now" or "2m ago". A card lands at its "at" second (seconds from the start of the video), growing out of the bottom of the screen (or out of the card already there) as on iOS 26; at 0 it is already there. While cards are on screen the lower half of the wallpaper darkens, as on the phone. At least one notification is required. The video ends "endHold" seconds (default 2) after the last card has settled.
Wallpaper and avatars are https image URLs or data: URIs (local file paths are not available). "wallpaper" also takes one of Apple's iOS 26 wallpapers by name ("sky", "shadow", "halo", "dusk", "yellow", "pink", "azure", "purple"); without one, "sky" (the iOS 26 default) is drawn, in its light or dark version with "theme". "avatar" on a notification shows the contact's photo with the app icon as a small badge. "display": "stack" folds the cards like iOS 26 does (the newest card, the next one or two as one-line rows under it, the rest counted as "+3 from WhatsApp and Messages"); "list" shows every card.
| Name | Required | Description | Default |
|---|---|---|---|
| dim | No | Black overlay on the wallpaper, 0 to 1. Default: 0. | |
| date | No | The line above the clock, written as iOS 26 does, e.g. "Tue Oct 6". Default: "Tue Oct 6". | |
| time | No | The big clock, without AM/PM, e.g. "9:41". Default: "9:41". | |
| frame | No | Frame index to capture, at 30 fps (e.g. 30 = one second in). Omit to capture the final frame, with every notification on screen. | |
| theme | No | The phone's appearance: "light" = frosted glass, "dark" = smoked glass, white text on both as on iOS 26; Apple's wallpapers follow it. Default: light. | |
| camera | No | Camera button bottom right. Default: true. | |
| sounds | No | The iOS notification tone when each card lands (video only). Default: true. | |
| carrier | No | Network name on the left of the status bar. Default: none. | |
| display | No | "list" shows every card, newest on top; "stack" is iOS 26's default fold: the newest card, the next one or two as one-line rows, the rest counted. Default: list. | |
| endHold | No | Seconds to hold on the last frame after the last card has settled. Default: 2. | |
| padlock | No | Small locked padlock above the date. Default: true. | |
| clockSize | No | Clock size in points on a 402 pt wide iPhone screen. Default: 100. | |
| statusBar | No | Right side of the status bar. (The clock there is not shown on a lock screen.) | |
| wallpaper | No | One of Apple's iOS 26 wallpapers by name ("sky", "shadow", "halo", "dusk", "yellow", "pink", "azure", "purple"), or a full-bleed image: URL or data: URI. Omitted: "sky", the iOS 26 default. | |
| clockColor | No | Clock colour (CSS colour). Default: "#FFFFFF". | |
| flashlight | No | Flashlight button bottom left. Default: true. | |
| wallpaperX | No | Where the crop is centred horizontally when the image is not the screen's shape, in % (50 = middle). Default: 50. | |
| wallpaperY | No | Where the crop is centred vertically, in % (50 = middle). Default: 50. | |
| clockWeight | No | Clock numeral weight, 100-900. Default: 760. | |
| clockOpacity | No | How much of the colour fills the Liquid Glass numerals, 0-1; the wallpaper shows through the rest. Default: 0.45. | |
| clockStretch | No | Vertical stretch of the clock numerals. Default: 1.16. | |
| notifications | Yes | The notifications, 1 to 20, in any order (they land in order of "at", ties keep the written order, and the newest sits on top). Lock screen format (an iOS 26 lock screen with notifications): The video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a see-through time such as "now" or "2m ago". A card lands at its "at" second (seconds from the start of the video), growing out of the bottom of the screen (or out of the card already there) as on iOS 26; at 0 it is already there. While cards are on screen the lower half of the wallpaper darkens, as on the phone. At least one notification is required. The video ends "endHold" seconds (default 2) after the last card has settled. Wallpaper and avatars are https image URLs or data: URIs (local file paths are not available). "wallpaper" also takes one of Apple's iOS 26 wallpapers by name ("sky", "shadow", "halo", "dusk", "yellow", "pink", "azure", "purple"); without one, "sky" (the iOS 26 default) is drawn, in its light or dark version with "theme". "avatar" on a notification shows the contact's photo with the app icon as a small badge. "display": "stack" folds the cards like iOS 26 does (the newest card, the next one or two as one-line rows under it, the rest counted as "+3 from WhatsApp and Messages"); "list" shows every card. | |
| wallpaperZoom | No | 1 = cover the screen, 2 = twice as close. Default: 1. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes meaningfully beyond the annotations: it discloses the return shape (PNG image content plus a text line with a URL that expires after 24 hours) and the error path (invalid input yields a validation-message error instead of an image). That is exactly the kind of context annotations don't carry. Minor gap: annotations declare readOnlyHint=false and idempotentHint=false for what reads as a pure render, and the description offers nothing to reconcile that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The opening two paragraphs are well front-loaded and earn their place. But the tool is a screenshot of a single frame, yet several paragraphs narrate video mechanics (card landing at 'at' seconds, endHold, notification tones), and the same block is then repeated inside the notifications schema — noticeable redundancy and wasted length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 23-parameter tool with nested objects and no output schema, the description does cover the return value (image + expiring URL), the error behavior, and the visual composition of the rendered lock screen. What's missing is the ecosystem context: how it relates to the sibling video/screenshot tools, which an agent needs to pick correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% across 23 parameters, so the schema already documents every field including 'frame' at 30 fps, the wallpaper name enum, and 'display'. The description largely restates the same information (the notifications/wallpaper/display block is duplicated verbatim in the schema), so it adds little beyond the structured data. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The first sentence gives a precise verb+resource+output: 'Render a single frame of an iOS lock screen with notifications to a PNG and return it as an image.' An agent immediately knows this produces a still PNG. However, there is no explicit differentiation from the sibling lockscreen_render_video, and the long subsequent text talks about 'the video' and card landing timings, which muddies whether this tool is the video one.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description never says when to choose this over lockscreen_render_video or reddit_screenshot / chat_screenshot. 'Defaults to the last frame — pass "frame" to capture an earlier moment' is parameter guidance, not usage guidance. No prerequisites, no exclusions, no alternative-tool routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Render a Reddit thread (script, or post+comments) to an MP4 and wait for it to finish. This queues a render, waits for it, and returns once it is done (or after failing/timing out). A short render typically takes 20-60 seconds.
Returns a public link to the MP4; the file is deleted after 24 hours. If txtreel is busy or you hit the rate limit, the result is an error with the message.
If the thread is invalid, this returns an error result with the validation messages (script errors are prefixed with the offending line number) instead of rendering.
Reddit thread script format (post + nested comments):
title: AITA for not going to my sister's wedding? body: First paragraph of the post (optional, one line per paragraph) body: Second paragraph [photo URL] a photo in the post (URL, file path or uploaded photo's number) sleepy_joe: A top-level comment
OP: A reply by the post's author (blue OP label)
sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age [91 more replies] collapsed replies under the comment above [pause 2] wait 2 s
The video is a screen recording of a thread on mobile reddit.com in iOS Safari: the page is laid out once and the view scrolls from block to block, holding each one long enough to read. The title is on screen from frame 0. Scores and ages left out of the script are generated (decreasing down the thread, never older than the post).
| Name | Required | Description | Default |
|---|---|---|---|
| post | No | The post. Use this OR script, not both. | |
| speed | No | Pacing multiplier; 2 = twice as fast, 0.5 = half speed. Default: 1. Use 1.3-1.5 for a faster reel. | |
| theme | No | Color theme, "light" or "dark". Default: light. | |
| script | No | Thread as a plain-text script. Use this OR post/comments, not both. Reddit thread script format (post + nested comments): title: AITA for not going to my sister's wedding? body: First paragraph of the post (optional, one line per paragraph) body: Second paragraph [photo URL] a photo in the post (URL, file path or uploaded photo's number) sleepy_joe: A top-level comment > OP: A reply by the post's author (blue OP label) >> sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age [91 more replies] collapsed replies under the comment above [pause 2] wait 2 s # comment The video is a screen recording of a thread on mobile reddit.com in iOS Safari: the page is laid out once and the view scrolls from block to block, holding each one long enough to read. The title is on screen from frame 0. Scores and ages left out of the script are generated (decreasing down the thread, never older than the post). | |
| endHold | No | Seconds to hold on the final frame before the video ends. Default: 2. | |
| comments | No | Comments as an array of event objects instead of a script string (use this OR script, not both). Each item is one of: {author, text, depth (0 top-level, 1 reply to the nearest depth-0 comment above, 2 reply to that, …), score?, age?, op?, avatar?, moreReplies?, hold?} or {type:"pause", seconds}. "op" or an author matching the post author gets the blue OP label automatically. | |
| statusBar | No | Phone status bar shown above the Safari toolbar. | |
| subreddit | No | The subreddit the thread is posted in. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no output schema, the description carries the return-value burden and does so: a public link to the MP4, deletion after 24 hours, synchronous queue-and-wait semantics, 20-60s typical duration, and distinct error results for busy/rate-limit versus invalid-thread validation. This goes well beyond the annotations (readOnlyHint=false, non-idempotent), which only signal that a render is a non-destructive but non-repeatable write.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded correctly: purpose and wait semantics come first, then return value, then errors, then format. However, the multi-line script-format example is reproduced verbatim from the schema's `script` field, which is wasted space in the description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex 8-parameter tool with nested objects, zero required params, and no output schema, the description covers what the agent most needs: what the call returns, how long it blocks, that the artifact expires in 24h, and how failures surface. Input-mode exclusivity is stated for both script and post/comments.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all 8 parameters including defaults and ranges; the baseline of 3 applies. The description's script-format block is largely a verbatim duplicate of the `script` property description rather than net-new parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource — 'Render a Reddit thread ... to an MP4 and wait for it to finish' — and names both supported input modes (script, or post+comments). The MP4/video framing inherently separates it from the sibling reddit_screenshot, even though that sibling is not named.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explains the two input modes and mutual exclusivity, plus failure behavior, but never says when to choose this over reddit_screenshot or chat_render_video. Usage context is implied by the 'MP4' output rather than stated as routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Render a single frame of a Reddit thread (script, or post+comments) to a PNG and return it as an image. Defaults to the last frame — pass "frame" to capture an earlier moment (30 fps).
Returns the PNG as image content, plus a text line with the PNG's URL (expires after 24 hours).
If the thread is invalid, this returns an error result with the validation messages instead of an image.
Reddit thread script format (post + nested comments):
title: AITA for not going to my sister's wedding? body: First paragraph of the post (optional, one line per paragraph) body: Second paragraph [photo URL] a photo in the post (URL, file path or uploaded photo's number) sleepy_joe: A top-level comment
OP: A reply by the post's author (blue OP label)
sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age [91 more replies] collapsed replies under the comment above [pause 2] wait 2 s
The video is a screen recording of a thread on mobile reddit.com in iOS Safari: the page is laid out once and the view scrolls from block to block, holding each one long enough to read. The title is on screen from frame 0. Scores and ages left out of the script are generated (decreasing down the thread, never older than the post).
| Name | Required | Description | Default |
|---|---|---|---|
| post | No | The post. Use this OR script, not both. | |
| frame | No | Frame index to capture, at 30 fps (e.g. 30 = one second in). Omit to capture the final frame of the thread. | |
| speed | No | Pacing multiplier; 2 = twice as fast, 0.5 = half speed. Default: 1. Use 1.3-1.5 for a faster reel. | |
| theme | No | Color theme, "light" or "dark". Default: light. | |
| script | No | Thread as a plain-text script. Use this OR post/comments, not both. Reddit thread script format (post + nested comments): title: AITA for not going to my sister's wedding? body: First paragraph of the post (optional, one line per paragraph) body: Second paragraph [photo URL] a photo in the post (URL, file path or uploaded photo's number) sleepy_joe: A top-level comment > OP: A reply by the post's author (blue OP label) >> sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age [91 more replies] collapsed replies under the comment above [pause 2] wait 2 s # comment The video is a screen recording of a thread on mobile reddit.com in iOS Safari: the page is laid out once and the view scrolls from block to block, holding each one long enough to read. The title is on screen from frame 0. Scores and ages left out of the script are generated (decreasing down the thread, never older than the post). | |
| endHold | No | Seconds to hold on the final frame before the video ends. Default: 2. | |
| comments | No | Comments as an array of event objects instead of a script string (use this OR script, not both). Each item is one of: {author, text, depth (0 top-level, 1 reply to the nearest depth-0 comment above, 2 reply to that, …), score?, age?, op?, avatar?, moreReplies?, hold?} or {type:"pause", seconds}. "op" or an author matching the post author gets the blue OP label automatically. | |
| statusBar | No | Phone status bar shown above the Safari toolbar. | |
| subreddit | No | The subreddit the thread is posted in. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnly=false, destructive=false, openWorld=false), it discloses the return shape (PNG image content plus a text URL that expires after 24 hours) and the failure behavior (invalid thread returns an error result with validation messages instead of an image). It also describes the rendered artifact as a mobile Safari screen recording with scroll-and-hold pacing, which an agent cannot infer from structured fields.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose and return behavior are front-loaded in the first two sentences, and the structure is easy to scan. The script-format block, however, is duplicated nearly verbatim from the schema's script parameter, which is repetition rather than added value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 9-parameter, nested-object tool with no output schema, the description covers return values, expiry, error behavior, and rendering semantics, so an agent can call it confidently. Minor gaps remain, such as not naming the video sibling as the alternative for full-length output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every parameter is already documented in the schema, and the description largely repeats the same material (script format, frame fps, theme/status-bar defaults). It adds little parameter-level meaning the schema lacks, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening sentence states a precise verb+resource+output ("Render a single frame of a Reddit thread ... to a PNG and return it as an image"). The emphasis on "single frame" implicitly but unambiguously separates it from the reddit_render_video sibling, and the description also clarifies the two input modes (post+comments vs script).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives clear operating context: default is the final frame, pass "frame" for an earlier moment at 30 fps, and "Use this OR script, not both" for the two input modes. It never explicitly names reddit_render_video as the alternative for full video, so there are no stated exclusions or alternative-routing rules.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
lockscreen_render_video8 fields changedInput schema / properties / clockOpacity / descriptionPrevious value: -"Clock opacity, 0-1; below 1 the wallpaper shows faintly through it. Default: 0.88."New value: +"How much of the colour fills the Liquid Glass numerals, 0-1; the wallpaper shows through the rest. Default: 0.45."Input schema / properties / clockStretch / descriptionPrevious value: -"Vertical stretch of the clock numerals. Default: 1.18."New value: +"Vertical stretch of the clock numerals. Default: 1.16."Input schema / properties / clockWeight / descriptionPrevious value: -"Clock numeral weight, 100-900. Default: 700."New value: +"Clock numeral weight, 100-900. Default: 760."Input schema / properties / date / descriptionPrevious value: -"The line above the clock, e.g. \"Tuesday, October 6\". Default: \"Tuesday, October 6\"."New value: +"The line above the clock, written as iOS 26 does, e.g. \"Tue Oct 6\". Default: \"Tue Oct 6\"."Input schema / properties / display / descriptionPrevious value: -"\"list\" shows every card; \"stack\" shows the newest with one or two slivers behind it. Default: list."New value: +"\"list\" shows every card, newest on top; \"stack\" is iOS 26's default fold: the newest card, the next one or two as one-line rows, the rest counted. Default: list."Input schema / properties / notifications / descriptionPrevious value: -"The notifications, 1 to 20, in any order (they land in order of \"at\", ties keep the written order, and the newest sits on top).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."New value: +"The notifications, 1 to 20, in any order (they land in order of \"at\", ties keep the written order, and the newest sits on top).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a see-through time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video), growing out of the bottom of the screen (or out of the card already there) as on iOS 26; at 0 it is already there. While cards are on screen the lower half of the wallpaper darkens, as on the phone. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). \"wallpaper\" also takes one of Apple's iOS 26 wallpapers by name (\"sky\", \"shadow\", \"halo\", \"dusk\", \"yellow\", \"pink\", \"azure\", \"purple\"); without one, \"sky\" (the iOS 26 default) is drawn, in its light or dark version with \"theme\". \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS 26 does (the newest card, the next one or two as one-line rows under it, the rest counted as \"+3 from WhatsApp and Messages\"); \"list\" shows every card."Input schema / properties / theme / descriptionPrevious value: -"Glass tint: \"light\" = pale glass with dark text, \"dark\" = smoked glass with white text. Default: light."New value: +"The phone's appearance: \"light\" = frosted glass, \"dark\" = smoked glass, white text on both as on iOS 26; Apple's wallpapers follow it. Default: light."Input schema / properties / wallpaper / descriptionPrevious value: -"Full-bleed wallpaper image: URL or data: URI. Omitted: a dark gradient."New value: +"One of Apple's iOS 26 wallpapers by name (\"sky\", \"shadow\", \"halo\", \"dusk\", \"yellow\", \"pink\", \"azure\", \"purple\"), or a full-bleed image: URL or data: URI. Omitted: \"sky\", the iOS 26 default."lockscreen_screenshot8 fields changedInput schema / properties / clockOpacity / descriptionPrevious value: -"Clock opacity, 0-1; below 1 the wallpaper shows faintly through it. Default: 0.88."New value: +"How much of the colour fills the Liquid Glass numerals, 0-1; the wallpaper shows through the rest. Default: 0.45."Input schema / properties / clockStretch / descriptionPrevious value: -"Vertical stretch of the clock numerals. Default: 1.18."New value: +"Vertical stretch of the clock numerals. Default: 1.16."Input schema / properties / clockWeight / descriptionPrevious value: -"Clock numeral weight, 100-900. Default: 700."New value: +"Clock numeral weight, 100-900. Default: 760."Input schema / properties / date / descriptionPrevious value: -"The line above the clock, e.g. \"Tuesday, October 6\". Default: \"Tuesday, October 6\"."New value: +"The line above the clock, written as iOS 26 does, e.g. \"Tue Oct 6\". Default: \"Tue Oct 6\"."Input schema / properties / display / descriptionPrevious value: -"\"list\" shows every card; \"stack\" shows the newest with one or two slivers behind it. Default: list."New value: +"\"list\" shows every card, newest on top; \"stack\" is iOS 26's default fold: the newest card, the next one or two as one-line rows, the rest counted. Default: list."Input schema / properties / notifications / descriptionPrevious value: -"The notifications, 1 to 20, in any order (they land in order of \"at\", ties keep the written order, and the newest sits on top).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."New value: +"The notifications, 1 to 20, in any order (they land in order of \"at\", ties keep the written order, and the newest sits on top).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a see-through time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video), growing out of the bottom of the screen (or out of the card already there) as on iOS 26; at 0 it is already there. While cards are on screen the lower half of the wallpaper darkens, as on the phone. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). \"wallpaper\" also takes one of Apple's iOS 26 wallpapers by name (\"sky\", \"shadow\", \"halo\", \"dusk\", \"yellow\", \"pink\", \"azure\", \"purple\"); without one, \"sky\" (the iOS 26 default) is drawn, in its light or dark version with \"theme\". \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS 26 does (the newest card, the next one or two as one-line rows under it, the rest counted as \"+3 from WhatsApp and Messages\"); \"list\" shows every card."Input schema / properties / theme / descriptionPrevious value: -"Glass tint: \"light\" = pale glass with dark text, \"dark\" = smoked glass with white text. Default: light."New value: +"The phone's appearance: \"light\" = frosted glass, \"dark\" = smoked glass, white text on both as on iOS 26; Apple's wallpapers follow it. Default: light."Input schema / properties / wallpaper / descriptionPrevious value: -"Full-bleed wallpaper image: URL or data: URI. Omitted: a dark gradient."New value: +"One of Apple's iOS 26 wallpapers by name (\"sky\", \"shadow\", \"halo\", \"dusk\", \"yellow\", \"pink\", \"azure\", \"purple\"), or a full-bleed image: URL or data: URI. Omitted: \"sky\", the iOS 26 default."lockscreen_render_video1 field changedInput schema / properties / notifications / descriptionPrevious value: -"The notifications, 1 to 20, in any order (they are shown oldest first by \"at\"; ties keep the written order).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."New value: +"The notifications, 1 to 20, in any order (they land in order of \"at\", ties keep the written order, and the newest sits on top).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."lockscreen_screenshot1 field changedInput schema / properties / notifications / descriptionPrevious value: -"The notifications, 1 to 20, in any order (they are shown oldest first by \"at\"; ties keep the written order).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."New value: +"The notifications, 1 to 20, in any order (they land in order of \"at\", ties keep the written order, and the newest sits on top).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."lockscreen_render_video2 fields changedInput schema / properties / notifications / descriptionPrevious value: -"The notifications, 1 to 20, in any order (they are shown oldest first by \"at\"; ties keep the written order).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock, flashlight and camera buttons). Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."New value: +"The notifications, 1 to 20, in any order (they are shown oldest first by \"at\"; ties keep the written order).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."Input schema / properties / wallpaperX / descriptionPrevious value: -"Where the crop is centred horizontally when the image is not 9:16, in % (50 = middle). Default: 50."New value: +"Where the crop is centred horizontally when the image is not the screen's shape, in % (50 = middle). Default: 50."lockscreen_screenshot2 fields changedInput schema / properties / notifications / descriptionPrevious value: -"The notifications, 1 to 20, in any order (they are shown oldest first by \"at\"; ties keep the written order).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock, flashlight and camera buttons). Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."New value: +"The notifications, 1 to 20, in any order (they are shown oldest first by \"at\"; ties keep the written order).\n\nLock screen format (an iOS 26 lock screen with notifications):\n\nThe video starts on a lock screen (wallpaper, big clock, date, padlock). Like the chat videos, the 9:16 video is the iPhone screen cut below the status bar and above the flashlight and camera buttons. Each notification is a Liquid Glass card from one app (imessage, whatsapp, instagram, chatgpt, claude, reddit, mail, phone, facetime, notes, reminders) with a bold title (usually the sender), a body of up to 4 lines, and a grey time such as \"now\" or \"2m ago\". A card lands at its \"at\" second (seconds from the start of the video) and springs in from the bottom; at 0 it is already there. At least one notification is required. The video ends \"endHold\" seconds (default 2) after the last card has settled.\n\nWallpaper and avatars are https image URLs or data: URIs (local file paths are not available). Without a wallpaper a dark gradient is drawn. \"avatar\" on a notification shows the contact's photo with the app icon as a small badge. \"display\": \"stack\" folds the cards like iOS does (newest on top with slivers behind); \"list\" shows every card."Input schema / properties / wallpaperX / descriptionPrevious value: -"Where the crop is centred horizontally when the image is not 9:16, in % (50 = middle). Default: 50."New value: +"Where the crop is centred horizontally when the image is not the screen's shape, in % (50 = middle). Default: 50."lockscreen_render_videolockscreen_screenshotchat_render_video1 field changedInput schema / properties / script / descriptionPrevious value: -"Conversation as a plain-text script. Use this OR messages, not both.\n\nConversation script format (one event per line):\n\nthem: hey, you up?\nme: yeah why\n[pause 1.5] wait 1.5 s\n--- Today 9:41 PM date/time separator\nme: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number)\n[them reacts ❤️] reaction on my last message\n[read] they read my messages\n=== everything above is already on screen at the start\n=== scroll 3 same, but open on the oldest message and skim down in 3 s\n# comment\n\n\"Name: text\" also means \"them\" when Name matches contact.name (e.g. contact.name \"Sam\" lets you write \"Sam: omg\" instead of \"them: omg\"). A literal \"\\n\" inside a message becomes a line break. Lines starting with # are comments.\n\nGuidance: one short message per line, like real texting — split up what a real person would send as separate texts rather than one long paragraph. A typical reel is 8-16 messages and 15-30 seconds. Use \"[pause N]\" to hold a beat before a reply lands (dramatic timing). Use \"===\" to start the video with everything above it already on screen, e.g. for a \"catch up on this conversation\" reel. Photos: \"me: [photo https://example.com/image.jpg] optional caption\" (https URLs only; local file paths are not available). Use \"=== scroll 3\" instead to open on the oldest message of a longer history and skim down to the live part in 3 s — too fast to read, so viewers pause and rewind (good for comments: hide a detail in the history). Leave keyboard at its default (true) so the newest messages stay above where the Reels caption/UI usually sits."New value: +"Conversation as a plain-text script. Use this OR messages, not both.\n\nConversation script format (one event per line):\n\nthem: hey, you up?\nme: yeah why\n[pause 1.5] wait 1.5 s\n--- Today 9:41 PM date/time separator\nme: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number)\n[them reacts ❤️] reaction on my last message\n[read] they read my messages\n=== everything above is already on screen at the start\n=== scroll 3 same, but open on the oldest message and skim down in 3 s\n# comment\n\n\"Name: text\" also means \"them\" when Name matches contact.name (e.g. contact.name \"Sam\" lets you write \"Sam: omg\" instead of \"them: omg\"). A literal \"\\n\" inside a message becomes a line break. Lines starting with # are comments.\n\nPhotos: \"me: [photo https://example.com/image.jpg] optional caption\" (https URLs only; local file paths are not available). \"=== scroll 3\" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits."chat_screenshot1 field changedInput schema / properties / script / descriptionPrevious value: -"Conversation as a plain-text script. Use this OR messages, not both.\n\nConversation script format (one event per line):\n\nthem: hey, you up?\nme: yeah why\n[pause 1.5] wait 1.5 s\n--- Today 9:41 PM date/time separator\nme: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number)\n[them reacts ❤️] reaction on my last message\n[read] they read my messages\n=== everything above is already on screen at the start\n=== scroll 3 same, but open on the oldest message and skim down in 3 s\n# comment\n\n\"Name: text\" also means \"them\" when Name matches contact.name (e.g. contact.name \"Sam\" lets you write \"Sam: omg\" instead of \"them: omg\"). A literal \"\\n\" inside a message becomes a line break. Lines starting with # are comments.\n\nGuidance: one short message per line, like real texting — split up what a real person would send as separate texts rather than one long paragraph. A typical reel is 8-16 messages and 15-30 seconds. Use \"[pause N]\" to hold a beat before a reply lands (dramatic timing). Use \"===\" to start the video with everything above it already on screen, e.g. for a \"catch up on this conversation\" reel. Photos: \"me: [photo https://example.com/image.jpg] optional caption\" (https URLs only; local file paths are not available). Use \"=== scroll 3\" instead to open on the oldest message of a longer history and skim down to the live part in 3 s — too fast to read, so viewers pause and rewind (good for comments: hide a detail in the history). Leave keyboard at its default (true) so the newest messages stay above where the Reels caption/UI usually sits."New value: +"Conversation as a plain-text script. Use this OR messages, not both.\n\nConversation script format (one event per line):\n\nthem: hey, you up?\nme: yeah why\n[pause 1.5] wait 1.5 s\n--- Today 9:41 PM date/time separator\nme: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number)\n[them reacts ❤️] reaction on my last message\n[read] they read my messages\n=== everything above is already on screen at the start\n=== scroll 3 same, but open on the oldest message and skim down in 3 s\n# comment\n\n\"Name: text\" also means \"them\" when Name matches contact.name (e.g. contact.name \"Sam\" lets you write \"Sam: omg\" instead of \"them: omg\"). A literal \"\\n\" inside a message becomes a line break. Lines starting with # are comments.\n\nPhotos: \"me: [photo https://example.com/image.jpg] optional caption\" (https URLs only; local file paths are not available). \"=== scroll 3\" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits."chat_validate1 field changedInput schema / properties / script / descriptionPrevious value: -"Conversation as a plain-text script. Use this OR messages, not both.\n\nConversation script format (one event per line):\n\nthem: hey, you up?\nme: yeah why\n[pause 1.5] wait 1.5 s\n--- Today 9:41 PM date/time separator\nme: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number)\n[them reacts ❤️] reaction on my last message\n[read] they read my messages\n=== everything above is already on screen at the start\n=== scroll 3 same, but open on the oldest message and skim down in 3 s\n# comment\n\n\"Name: text\" also means \"them\" when Name matches contact.name (e.g. contact.name \"Sam\" lets you write \"Sam: omg\" instead of \"them: omg\"). A literal \"\\n\" inside a message becomes a line break. Lines starting with # are comments.\n\nGuidance: one short message per line, like real texting — split up what a real person would send as separate texts rather than one long paragraph. A typical reel is 8-16 messages and 15-30 seconds. Use \"[pause N]\" to hold a beat before a reply lands (dramatic timing). Use \"===\" to start the video with everything above it already on screen, e.g. for a \"catch up on this conversation\" reel. Photos: \"me: [photo https://example.com/image.jpg] optional caption\" (https URLs only; local file paths are not available). Use \"=== scroll 3\" instead to open on the oldest message of a longer history and skim down to the live part in 3 s — too fast to read, so viewers pause and rewind (good for comments: hide a detail in the history). Leave keyboard at its default (true) so the newest messages stay above where the Reels caption/UI usually sits."New value: +"Conversation as a plain-text script. Use this OR messages, not both.\n\nConversation script format (one event per line):\n\nthem: hey, you up?\nme: yeah why\n[pause 1.5] wait 1.5 s\n--- Today 9:41 PM date/time separator\nme: [photo URL] caption a photo (URL, local file path, or an uploaded photo's number)\n[them reacts ❤️] reaction on my last message\n[read] they read my messages\n=== everything above is already on screen at the start\n=== scroll 3 same, but open on the oldest message and skim down in 3 s\n# comment\n\n\"Name: text\" also means \"them\" when Name matches contact.name (e.g. contact.name \"Sam\" lets you write \"Sam: omg\" instead of \"them: omg\"). A literal \"\\n\" inside a message becomes a line break. Lines starting with # are comments.\n\nPhotos: \"me: [photo https://example.com/image.jpg] optional caption\" (https URLs only; local file paths are not available). \"=== scroll 3\" opens on the oldest message of a longer history and skims down to the live part in 3 s. With keyboard true (the default), the newest messages stay above the area where the Reels caption sits."reddit_render_video1 field changedInput schema / properties / script / descriptionPrevious value: -"Thread as a plain-text script. Use this OR post/comments, not both.\n\nReddit thread script format (post + nested comments):\n\ntitle: AITA for not going to my sister's wedding?\nbody: First paragraph of the post (optional, one line per paragraph)\nbody: Second paragraph\n[photo URL] a photo in the post (URL, file path or uploaded photo's number)\nsleepy_joe: A top-level comment\n> OP: A reply by the post's author (blue OP label)\n>> sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age\n[91 more replies] collapsed replies under the comment above\n[pause 2] wait 2 s\n# comment\n\nThis is a screen recording of someone reading a real-looking thread on mobile reddit.com in iOS Safari: the page is laid out once and the camera scrolls from block to block, holding each one long enough to read. The title is the hook and is on screen from frame 0 — make it count. A typical reel is a post with 1-3 short body paragraphs plus 4-10 comments, about 30-60 seconds. Use nested replies (\">\", \">>\", …) and a reply from the post's author (\"> OP: …\") for drama — someone getting called out and the poster jumping in reads as real. A \"[N more replies]\" line under a comment adds realism: it's what a real collapsed thread looks like. Leave scores and ages out unless they matter to the story — they're made up realistically (decreasing down the thread, never older than the post) when omitted. Use \"speed\" 1.3-1.5 for a faster-paced reel."New value: +"Thread as a plain-text script. Use this OR post/comments, not both.\n\nReddit thread script format (post + nested comments):\n\ntitle: AITA for not going to my sister's wedding?\nbody: First paragraph of the post (optional, one line per paragraph)\nbody: Second paragraph\n[photo URL] a photo in the post (URL, file path or uploaded photo's number)\nsleepy_joe: A top-level comment\n> OP: A reply by the post's author (blue OP label)\n>> sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age\n[91 more replies] collapsed replies under the comment above\n[pause 2] wait 2 s\n# comment\n\nThe video is a screen recording of a thread on mobile reddit.com in iOS Safari: the page is laid out once and the view scrolls from block to block, holding each one long enough to read. The title is on screen from frame 0. Scores and ages left out of the script are generated (decreasing down the thread, never older than the post)."reddit_screenshot1 field changedInput schema / properties / script / descriptionPrevious value: -"Thread as a plain-text script. Use this OR post/comments, not both.\n\nReddit thread script format (post + nested comments):\n\ntitle: AITA for not going to my sister's wedding?\nbody: First paragraph of the post (optional, one line per paragraph)\nbody: Second paragraph\n[photo URL] a photo in the post (URL, file path or uploaded photo's number)\nsleepy_joe: A top-level comment\n> OP: A reply by the post's author (blue OP label)\n>> sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age\n[91 more replies] collapsed replies under the comment above\n[pause 2] wait 2 s\n# comment\n\nThis is a screen recording of someone reading a real-looking thread on mobile reddit.com in iOS Safari: the page is laid out once and the camera scrolls from block to block, holding each one long enough to read. The title is the hook and is on screen from frame 0 — make it count. A typical reel is a post with 1-3 short body paragraphs plus 4-10 comments, about 30-60 seconds. Use nested replies (\">\", \">>\", …) and a reply from the post's author (\"> OP: …\") for drama — someone getting called out and the poster jumping in reads as real. A \"[N more replies]\" line under a comment adds realism: it's what a real collapsed thread looks like. Leave scores and ages out unless they matter to the story — they're made up realistically (decreasing down the thread, never older than the post) when omitted. Use \"speed\" 1.3-1.5 for a faster-paced reel."New value: +"Thread as a plain-text script. Use this OR post/comments, not both.\n\nReddit thread script format (post + nested comments):\n\ntitle: AITA for not going to my sister's wedding?\nbody: First paragraph of the post (optional, one line per paragraph)\nbody: Second paragraph\n[photo URL] a photo in the post (URL, file path or uploaded photo's number)\nsleepy_joe: A top-level comment\n> OP: A reply by the post's author (blue OP label)\n>> sleepy_joe [2.1K 3h]: A reply to that reply, with its votes and age\n[91 more replies] collapsed replies under the comment above\n[pause 2] wait 2 s\n# comment\n\nThe video is a screen recording of a thread on mobile reddit.com in iOS Safari: the page is laid out once and the view scrolls from block to block, holding each one long enough to read. The title is on screen from frame 0. Scores and ages left out of the script are generated (decreasing down the thread, never older than the post)."chat_render_videochat_screenshotchat_validatereddit_render_videoreddit_screenshotFake chat videos (WhatsApp, iMessage, ChatGPT…) exported as MP4, GIF or transparent WebM / MOV.
Public Instagram reels, posts, profiles and comments, plus reel-to-text transcripts. No login.
Instagram, WhatsApp and Messenger DMs through official Meta Business APIs.
Instagram, X, TikTok, YouTube, Facebook and Reddit data. Approved OAuth or API-key access required.
Add one secure layer between your agents and this server.
