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

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

activate_listing

Publish a draft or inactive Etsy listing to make it active. Preview with confirm=false before confirming; activation incurs an Etsy listing fee.

Instructions

Publish a draft or inactive listing (state -> active). COSTS AN ETSY LISTING FEE. confirm=false 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>"
    },
    "name": "activate_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse (default) only returns a preview of the request. true sends it.
listing_idYesListing id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds two genuinely new facts — that publishing incurs an Etsy listing fee and that confirm=false is a safe preview. It stops short of saying whether the fee is charged per activation attempt or how failures behave, keeping it below a 5.

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?

Two short sentences with the state transition front-loaded and the high-stakes cost warning capitalized so it cannot be skimmed past. No filler or redundant restatement of the tool name.

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 2-parameter tool with full schema coverage, no output schema and annotations covering safety, this covers what an agent needs: eligibility, terminal state, cost, and the preview path. A brief note on what to call to undo (deactivate/update_listing) would make it complete.

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 100%, so both parameters are already documented, including confirm's preview semantics. The description's "confirm=false previews" only restates the schema's own wording, adding no new meaning; baseline 3 applies.

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 ("Publish") plus the resource and the exact state transition (state -> active), and clarifies which listings are eligible (draft or inactive). An agent can distinguish this from update_listing or create_draft_listing without opening either schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it applies to draft/inactive listings and offers confirm=false as a preview step, which is actionable guidance. However, it never contrasts with the sibling update_listing (which could also set state) or states preconditions such as required scopes, so no explicit when-not guidance exists.

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