Skip to main content
Glama
Sign In

Pixly

by app.pixly
OverviewDiscussionsAdmin

List Library

list_library
Read-onlyIdempotent

List the user's recent generations, or with type "uploads" their own uploaded source photos, newest first. Uploads are the way in when the photo is a local file: connectors cannot send bytes, so the user adds it at https://pixly.app/app and you pick up the r2Path here.

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by media type. "uploads" lists the user's own source photos instead of generations — use it when they refer to a photo they added but have not run a tool on yet.
limitNo
listingIdNoOnly this property folder's results and photos (from list_listings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / listingId
      Added value: +{
+  "description": "Only this property folder's results and photos (from list_listings)",
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds context the annotations cannot carry: uploads must be added by the user at the web app, connectors cannot send bytes, and the r2Path is available here — genuinely useful workflow behavior.

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?

Two sentences, front-loaded with the core purpose before the uploads explanation. The second sentence is somewhat dense/run-on but every clause carries information an agent needs to handle local-file uploads.

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?

For a read-only list tool with no output schema, the description covers the two list modes and the upload workflow, implying r2Path is returned. It omits pagination/limit behavior, but overall it gives enough for correct 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 67%; the schema already documents 'type' and 'listingId'. The description reinforces the 'uploads' meaning and adds the 'newest first' ordering, but says nothing about the undocumented 'limit' parameter or its cap, so it does not fully compensate for the coverage gap.

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?

States a specific verb and resource ('List the user's recent generations', or 'uploads' for source photos, 'newest first') so the agent knows exactly what is returned. It distinguishes the uploads mode from the generations mode, though it does not explicitly contrast with siblings like list_listings or view_pixly_photo.

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 when-to-use condition for the 'uploads' type: 'the way in when the photo is a local file', because 'connectors cannot send bytes'. This routes the agent usefully, but it offers no exclusions or explicit alternatives when the agent should instead call list_listings or view_pixly_photo.

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