Skip to main content
Glama
Sign In
etsy-clean-mcp

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

upload_listing_image

Uploads a JPG, PNG, GIF, or WebP image to an Etsy listing and previews the request before sending it for confirmation.

Instructions

Upload a jpg/png/gif/webp image to a listing. The file must be inside the upload folder (/root/Etsy/upload); relative paths are taken from there. confirm=false checks the file and previews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listing_id": "<listing_id>",
      "path": "<path>"
    },
    "name": "upload_listing_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesImage file inside the upload folder.
rankNoPosition, 1 = main image.
confirmNofalse (default) only returns a preview of the request. true sends it.
alt_textNo
listing_idYesListing id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, open-world operation; the description adds the crucial dry-run semantics (confirm=false previews rather than sends) and the sandboxing rule that files must live in /root/Etsy/upload. It stops short of saying what a successful upload returns or whether existing images are replaced.

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: what it does, where files must live, and what the confirm flag does. Every sentence carries information and the format/scope constraint is front-loaded.

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 5-parameter upload tool with annotations and no output schema, the definition covers formats, path resolution, required vs optional behavior, and the preview workflow. The only shortfall is not indicating what a successful call returns or how image rank interacts with existing images.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 80% schema coverage the baseline is 3; the description earns an extra point by clarifying that relative paths resolve against /root/Etsy/upload, which is stronger than the schema's 'Image file inside the upload folder', and by explaining the confirm parameter's preview-vs-send behavior.

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 (upload) plus the resource (image to a listing) and even enumerates accepted formats (jpg/png/gif/webp). No sibling tool deals with images, so this is unambiguous without further differentiation.

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?

Explains the two-step workflow: confirm=false validates and previews, an explicit send happens only when confirmed. It does not name alternatives, but none of the listed siblings perform image uploads, so the only gap is the absence of an explicit 'when to use this instead of X' clause.

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

Deploy Server

Other Tools