Skip to main content
Glama

Pixly

by app.pixly
OverviewDiscussionsAdmin

Photo to Video

photo_to_video

Turn a start photo — and optionally an end photo — into a video. With an end photo the camera travels from the first photo and lands exactly on the second (e.g. two views of the same kitchen → an orbit around the island). Pick a ready-made camera move or write your own prompt; choose the model, length and sound. Costs credits from the user's Pixly balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNokling-v3: 3/5/8/10/15 s, optional sound, lands most precisely on the end frame. kling-2.6: 5/10 s, silent, cheaper.kling-v3
soundNoAdd ambient sound (kling-v3 only; kling-2.6 is always silent).
formatNoLabel for the clip's shape; the video follows the start photo's own shape.16:9
promptNoYour own description of the video, in any language. Replaces cameraMove when set.
r2PathNoStorage path of a photo already in the user's Pixly library (from list_library, or returned by an upload ticket) — the alternative to imageUrl.
imageUrlNoStart frame — where the video begins. Public https URL or data: URI; either imageUrl or r2Path is required.
endR2PathNoR2 path of the end frame — the alternative to endImageUrl.
cameraMoveNoReady-made camera move used when no prompt is given.smooth
endImageUrlNoOptional end frame — the camera travels from the start photo and lands exactly on this one. Best when both photos show the same space from different spots.
durationSecondsNoClip length. kling-v3 takes 3, 5, 8, 10 or 15; kling-2.6 takes 5 or 10.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
typeNo
errorNo
jobIdYesPass to get_job to poll
statusYespending | processing | completed | failed — anything not completed/failed is still running
createdAtNo
resultUrlsNoPresent when completed; valid 7 days
completedAtNo
creditsChargedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / r2Path / description
      Previous value: -"R2 object path from an upload ticket (the create_upload_ticket tool, or POST /api/v1/uploads over REST) — the alternative to imageUrl when the photo is a local file."New value: +"Storage path of a photo already in the user's Pixly library (from list_library, or returned by an upload ticket) — the alternative to imageUrl."
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / r2Path / description
      Previous value: -"R2 object path from an upload ticket (POST /api/v1/uploads) — the alternative to imageUrl when the photo is a local file."New value: +"R2 object path from an upload ticket (the create_upload_ticket tool, or POST /api/v1/uploads over REST) — the alternative to imageUrl when the photo is a local file."
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the operation 'Costs credits from the user's Pixly balance,' a meaningful side effect an agent must know. It also reveals the camera behavior of landing exactly on the end photo. It does not mention asynchronous execution or failure modes, but with an output schema present and annotations already covering read-only and destructive hints, this is a strong addition.

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?

The description is compact and well-structured: a first sentence stating the core transformation, a second illustrating the end-photo use case, and a third covering the main choices and cost. It is front-loaded with the purpose and contains no filler or redundant sentences.

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?

Given 10 parameters, full schema coverage, and an output schema, the description provides the essential high-level orientation: input photos, optional end photo, camera movement options, model/length/sound choices, and the credit cost. It does not spell out the two input-path alternatives (imageUrl vs r2Path), but those are thoroughly documented in the schema, so the description is largely complete for selection and initial invocation.

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 main description adds conceptual context, such as the end-photo orbit example and the general choices of model, length, and sound, but it does not add parameter-level detail beyond what the schema already provides. The schema descriptions themselves are rich and handle the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Turn a start photo — and optionally an end photo — into a video,' which is a specific verb and resource that clearly identifies the tool's core purpose. It adds distinctive behavior by describing the camera traveling from the first photo and landing exactly on the second, and it mentions camera moves, prompts, model/length/sound. However, it never explicitly contrasts itself with sibling tools like cinematic_motion, so differentiation is implied rather than directly stated.

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?

The description gives clear context for when to use the tool: converting a photo, and optionally a second photo, into a video, with an example of two kitchen views becoming an orbit. It also explains the choice between a camera move and a custom prompt. But it does not explicitly state when to prefer this tool over siblings like before_after_reel or cinematic_motion, nor does it list exclusions.

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

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