JANCTION Render

Share a render

render_share

Publish a finished render as a public web page anyone with the link can open (for X, Discord or a client): the image or video, the render settings, an optional title and note, the user's request in their words (prompt), and the bpy script only if include_script=True. The page keeps its own copy of the result after the job's files expire, until render_unshare. listed=True only asks to appear in the public gallery; the operator reviews it first. Public: ask the user before sharing and return the url to them. Only the key that rendered the job can share it.

Input Schema

Name	Required	Description
`note`	No	A sentence shown under the image on the share page (optional).
`title`	No	Title shown on the public share page (optional).
`job_id`	Yes	The job_id returned by render_preview or render_final (j_...; a long final split into parts is b_...). Only this key's jobs; in render_status, leave it empty to list them.
`listed`	No	True asks for the page to appear in the public gallery after the operator reviews it.
`prompt`	No	What the user asked you, in their words (shown as 'what the user asked the agent').
`include_script`	No	True also publishes the bpy script on the share page.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / job_id / description

Previous value: -"The job_id returned by render_preview or render_final (j_...; a long final split into parts is b_...). Only this key's jobs."New value: +"The job_id returned by render_preview or render_final (j_...; a long final split into parts is b_...). Only this key's jobs; in render_status, leave it empty to list them."

Changed1 schema field changedOct 13, 2026

changedInput schema / properties / job_id / description

Previous value: -"The job_id returned by render_preview or render_final (looks like j_...)."New value: +"The job_id returned by render_preview or render_final (j_...; a long final split into parts is b_...). Only this key's jobs."

Changed6 schema fields changedOct 7, 2026

addedInput schema / properties / include_script / description

Added value: +"True also publishes the bpy script on the share page."

addedInput schema / properties / job_id / description

Added value: +"The job_id returned by render_preview or render_final (looks like j_...)."

addedInput schema / properties / listed / description

Added value: +"True asks for the page to appear in the public gallery after the operator reviews it."

addedInput schema / properties / note / description

Added value: +"A sentence shown under the image on the share page (optional)."

addedInput schema / properties / prompt / description

Added value: +"What the user asked you, in their words (shown as 'what the user asked the agent')."

addedInput schema / properties / title / description

Added value: +"Title shown on the public share page (optional)."

First observedOct 2, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing the public-exposure consequence, the persistence rule ('keeps its own copy of the result after the job's files expire, until render_unshare'), the operator-review gate on gallery listing, and the authorization constraint that only the rendering key can share.

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?

Single dense paragraph, correctly front-loaded with what gets published before the qualifiers. The run-on ':'-chained clauses pack a lot in but every clause adds real information, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with full annotation coverage, full schema coverage and an output schema, the description covers the remaining agent-relevant unknowns: public exposure, persistence, auth constraint, and user-consent requirement. Nothing needed to invoke it safely is missing.

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 the baseline is 3. The description reinforces include_script=True, listed=True, and prompt semantics, but that meaning largely duplicates the schema's own parameter descriptions rather than adding new syntax or format detail.

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?

States a specific verb and resource ('Publish a finished render as a public web page'), enumerates exactly what the page contains, and names render_unshare as the lifecycle counterpart, so an agent can separate it from render_download or render_unshare without opening another schema.

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?

Gives real usage conditions: 'ask the user before sharing and return the url to them', and clarifies that listed=True merely asks for gallery inclusion subject to operator review. It stops short of explicitly routing between this tool and siblings like render_download or render_final, so 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All JANCTION Render 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.