Pixly

Watermark Photos

watermark_photos

Free (no credits): put the agent's or agency's mark on listing photos — text (name, phone) and/or the logo saved on their Pixly account — in a corner or the middle, up to 10 photos per call. Returns every marked photo at once.

Input Schema

Name	Required	Description	Default
`size`	No		medium
`text`	No	The text, e.g. "Smith Realty · 555-0100". Optional when the account has a saved logo.
`photos`	Yes	The photos to mark, 1–10. Each item takes imageUrl or r2Path.
`useLogo`	No	Add the logo saved on the account (Pixly floor plan settings), when there is one.
`position`	No		bottom-right
`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"
+}

AddedOct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the safety profile (non-read-only, non-destructive, non-idempotent, open-world), so the bar is lower. The description adds cost behavior ('Free (no credits)') and batching behavior ('Returns every marked photo at once'), which are not derivable from annotations. It still omits whether originals are modified versus a new copy produced.

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?

A single, tightly constructed sentence with the cost signal front-loaded ahead of the functional detail. Every clause carries information — mark content, placement, per-call limit, and return behavior — with no filler.

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?

An output schema exists, so return-value detail is not required, though the description still notes batch return. For a 6-parameter tool with a nested photo array, it covers the core interaction well but leaves gaps around source-photo handling, size parameter intent, and auth requirements.

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 coverage is 67%, above the 50% floor but well below the 80% baseline, so the schema does much of the work on r2Path/imageUrl/useLogo/listingId. The description only adds natural-language reinforcement for text (name, phone), position (corner or middle), and the 10-photo cap, without elaborating on defaults or the size/logos interplay.

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 ('put the agent's or agency's mark on listing photos') and enumerates the mark types (text name/phone, saved logo), so an agent immediately understands this overlays branding. It is clearly distinct from other image siblings like blur_faces_plates or plot_sign, which redact or add physical signage rather than apply an ownership watermark.

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 a decision-relevant cue — 'Free (no credits)' — which helps an agent prefer this over credit-consuming siblings, and the 'up to 10 photos per call' hints at batching. However, it never states when to use this instead of alternatives, nor any prerequisites or exclusions, leaving usage to inference.

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?