Pixly

Before/After Reel

before_after_reel

Before and after video: animate a before→after transformation (e.g. empty room → staged, or a renovation) into a social-ready reveal reel from two photos. Costs credits from the user's Pixly balance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No		9:16
`afterR2Path`	No	R2 path of the end frame — the alternative to afterImageUrl.
`revealStyle`	No	How the transformation is revealed	smooth
`videoIntent`	No		staging_reveal
`beforeR2Path`	No	R2 path of the start frame — the alternative to beforeImageUrl.
`afterImageUrl`	No	End frame (e.g. the staged result) — https URL or data: URI
`beforeImageUrl`	No	Start frame (e.g. the empty room photo) — https URL or data: URI
`durationSeconds`	No

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`type`	No
`error`	No
`jobId`	Yes	Pass to get_job to poll
`status`	Yes	pending \| processing \| completed \| failed — anything not completed/failed is still running
`createdAt`	No
`resultUrls`	No	Present when completed; valid 7 days
`completedAt`	No
`creditsCharged`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "completedAt": {
+      "type": "string"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "creditsCharged": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "error": {
+      "type": "string"
+    },
+    "jobId": {
+      "description": "Pass to get_job to poll",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "resultUrls": {
+      "description": "Present when completed; valid 7 days",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "pending | processing | completed | failed — anything not completed/failed is still running",
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "jobId",
+    "status"
+  ],
+  "type": "object"
+}

First observedAug 12, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds a key behavioral detail beyond annotations: it costs credits from the user's Pixly balance. It also communicates that the result is a reel, but does not cover job lifecycle or failure behavior; annotations already handle readOnly/destructive hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler: purpose, use case examples, and cost are all included. The most important information is front-loaded.

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?

The description is complete enough for a tool with a detailed schema and output schema: it conveys purpose, examples, and cost. It lacks alternative guidance and some parameter trade-off context, but those are secondary given the structured schema.

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 63% and the description adds conceptual context by tying 'two photos' to the before/after inputs. However, it does not explain format, revealStyle, duration, or the R2-path vs URL alternatives beyond what the schema already provides.

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 description states a specific action: animate a before→after transformation from two photos into a social-ready reveal reel. It gives concrete examples (empty room → staged, renovation) and the phrase 'before→after video' clearly distinguishes it from generic siblings like photo_to_video or virtual_staging.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage through examples and the mention of a social-ready reel, but it never names alternatives or says when not to use this tool. With many sibling tools like photo_to_video, an agent would benefit from explicit routing guidance.

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

All Pixly 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?