Pixly

Sky Replacement

replace_sky

Replace a grey, overcast or blown-out sky in an exterior listing photo with a natural clear blue sky, matching the light and keeping the building, trees and reflections unchanged. A run takes about 1–2 minutes; poll get_job until it completes. Costs credits from the user's Pixly balance.

Input Schema

Name	Required	Description	Default
`sky`	No	Sky style. 'auto' lets the tool pick what suits the photo's light.	auto
`sun`	No	Sun glow: auto (a glow for sunset/sunrise styles, none otherwise), on (place it with sunX/sunY), off.	auto
`sunX`	No	With sun=on: glow position from the left edge, 0..1.
`sunY`	No	With sun=on: glow position from the top edge, 0..1 (kept in the top 60%).
`r2Path`	No	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.
`imageUrl`	No	Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required.
`listingId`	No	A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves.

Output Schema

Name	Required	Description
`jobs`	No	Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results
`note`	No
`type`	No
`error`	No
`jobId`	Yes	Pass to get_job to poll
`quote`	No	Present when status is "awaiting_confirmation": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm
`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
`resultPaths`	No	Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result
`creditsCharged`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedInput schema / properties / listingId

Added value: +{
+  "description": "A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves.",
+  "type": "string"
+}

addedOutput schema / properties / jobs

Added value: +{
+  "description": "Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / quote

Added value: +{
+  "description": "Present when status is \"awaiting_confirmation\": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm",
+  "type": "object"
+}

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / resultPaths

Added value: +{
+  "description": "Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 23, 2026

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

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"
+}

Changed1 schema field changedSep 20, 2026

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

AddedSep 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only establish that this is a non-destructive write; the description adds the traits an agent actually needs: a 1–2 minute asynchronous runtime with a required get_job polling loop, and credit consumption from the user's Pixly balance. It also discloses what is preserved (building, trees, reflections), which the annotations cannot convey.

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?

Three tight sentences, each earning its place: what it does, how long it takes and how to wait, and what it costs. The purpose is front-loaded ahead of the operational and billing details.

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?

An output schema exists, so return values need no explanation, and the description fills the remaining gaps an agent needs for a 7-parameter async, credit-consuming tool: latency, polling protocol and cost.

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 schema already documents every parameter including the enums, sunX/sunY semantics and the imageUrl/r2Path requirement. The description only indirectly touches parameters via 'matching the light', which loosely maps to the sun=auto behavior, so baseline 3 is appropriate.

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 ('replace ... sky in an exterior listing photo') plus the exact input condition (grey, overcast or blown-out) and the preservation guarantee. It is clearly distinguishable from sibling tools such as day_to_night, reset_season and replace_lawn.

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 a clear triggering condition ('grey, overcast or blown-out sky in an exterior listing photo') and the operational follow-up ('poll get_job until it completes'). It does not name alternative tools (e.g. day_to_night) or state when not to use it, so it stops short of a 5.

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?