txtreel

Screenshot a Reddit thread

reddit_screenshot

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

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).

Input Schema

Name	Required	Description
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / script / description

Previous 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)."

First observedSep 29, 2026

TDQS

A4.3/5.0

Behavior5/5

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.

Conciseness4/5

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.

Completeness4/5

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.

Parameters3/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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.

All txtreel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?