Skip to main content
Glama

etsy_user_address_delete

Destructive

Remove a user's shipping address from Etsy by specifying the user ID and address ID.

Instructions

Delete a user address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
user_address_idYes
Behavior3/5

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

The annotation 'destructiveHint: true' already informs the agent that this tool performs a destructive action. The description 'Delete a user address' matches this but adds no additional behavioral context beyond what the annotation provides, such as irreversibility 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at one phrase, but it is too minimal. While it avoids verbosity, it lacks substance and detail that would justify a higher score. Every word is necessary, but more information is needed.

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?

Given that there is no output schema and no parameter descriptions, the description is incomplete. A delete tool should at least mention irreversibility or confirmation requirements. The annotations partially compensate, but the description does not provide enough context for an AI agent to use the tool safely and effectively.

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

Parameters1/5

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

The description does not explain the meaning or usage of the two parameters (user_id, user_address_id) beyond what is in the schema. With 0% schema description coverage, the description fails to compensate, leaving the agent without critical context for correct invocation.

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?

The description states 'Delete a user address', which clearly indicates the action and resource. However, it does not differentiate this tool from related tools like etsy_user_addresses_list or etsy_user_address_get, as there are no siblings mentioned or contrast provided.

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?

The description offers no guidance on when to use this tool versus alternatives. There is no context about prerequisites, when deletion is appropriate, or situations where other address tools should be used instead.

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/BusyBee3333/etsy-mcp-2026-complete'

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