Rarely needed: generation tools take an imageUrl directly. Use this only to import a photo into Pixly ahead of time, e.g. to reuse one URL across several tools without refetching it each time.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Publicly reachable image URL (JPG/PNG/WebP, max 10 MB) to import into Pixly |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a mutation (readOnlyHint: false). The description adds behavioral context by noting that importing avoids 'refetching' the URL each time, implying the image is stored/cached in Pixly. It does not contradict the annotations and adds value beyond the safety hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the key point ('Rarely needed') and no redundant wording. Every phrase earns its place, providing purpose and usage guidance in a compact form.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description covers purpose, usage context, and a hint of behavioral implications. It lacks explicit mention of the return value or post-import behavior, but given the low complexity and rich schema, it remains adequately complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents the 'url' parameter with format, accepted types, max size, and reachability constraints (100% coverage). The description adds no additional parameter-level detail, so it relies on the schema—fitting the baseline of 3 for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: import a photo into Pixly ahead of time. It uses the specific verb 'import' and the resource 'photo into Pixly', and explicitly distinguishes itself from generation tools that accept an imageUrl directly, making it easy to understand when this tool is needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description opens with 'Rarely needed' and explicitly states when to use it (to reuse a URL across several tools without refetching) and when not to (generation tools already take an imageUrl directly). This provides clear, actionable guidance on tool selection relative to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct workflow: uploads, job/credit management, single-effect photo edits, staging, and video generation. The only mild ambiguity is between declutter_photo and remove_furniture, but the descriptions explicitly contrast them, so an agent can usually pick correctly.
Most tools follow a clear verb_noun snake_case pattern like create_upload_ticket, replace_sky, and remove_furniture. A few names are noun phrases rather than verbs—day_to_night, virtual_staging, before_after_reel—but they are still readable and do not break the overall convention badly.
At 15 tools, the server is at the upper edge of the ideal range, but every tool maps to a distinct real-estate photo/video workflow: uploading, credits, job polling, staging, editing, and reveal videos. Nothing feels redundant or unnecessary.
The core Pixly workflow is well covered: bring images in via upload, run generation/editing tools, poll jobs, and list results. Minor gaps like job cancellation or generic restyle control exist, but agents can complete the primary photo and video workflows end to end.
