Skip to main content
Glama
DColl

etsy-mcp-server

by DColl

upload_listing_image

Upload an image to an Etsy listing from your local file path. Specify the listing ID, image path, and optional rank or overwrite to manage display order.

Instructions

Upload an image to a listing from a local file path. Supported formats: JPEG, PNG, GIF (max 10MB).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rankNoDisplay order (1 = main image)
overwriteNoReplace existing image at this rank
image_pathYesAbsolute or relative path to the image file on your machine
listing_idYes
Behavior2/5

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

No annotations provided. Description lacks details on whether uploads are additive or destructive, or how the 'overwrite' parameter behaves. Does not mention required permissions or side effects.

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?

Single sentence conveys core purpose and constraints efficiently. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 parameters, no output schema, and no annotations, the description is insufficiently complete. Missing details on error handling, outcome, and behavior of optional parameters.

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 75%, so the schema already documents most parameters. The description adds no additional meaning beyond the schema, meeting baseline.

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?

Clearly states the action (upload), resource (image to listing), and constraints (local file path, supported formats, max size). Distinguishes from sibling 'upload_listing_file' by specifying image formats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool over alternatives like 'upload_listing_file' or other listing operations. Implies local file only but doesn't address URL-based uploads.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DColl/etsy-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server