delete_section
Remove an Etsy shop section; its listings become unsectioned.
Instructions
Delete a shop section. Listings in this section will become unsectioned.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| section_id | Yes |
Remove an Etsy shop section; its listings become unsectioned.
Delete a shop section. Listings in this section will become unsectioned.
| Name | Required | Description | Default |
|---|---|---|---|
| section_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It discloses that listings become unsectioned, but lacks details on irreversibility, error cases, or authorization needs. Adequate but incomplete.
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?
Two sentences, no wasted words. Efficient and front-loaded.
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-param tool, the description explains the effect on listings but omits return value, error handling, and confirmation. Moderately complete given simplicity.
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?
Schema description coverage is 0%, but the description adds no meaning to the `section_id` parameter beyond its name (e.g., format, source, validation).
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 action ('Delete a shop section') and the resource. It correctly distinguishes from sibling tools like create_section, update_section, and list_sections.
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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or conditions (e.g., section must exist, impact on listings).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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