Skip to main content
Glama

Growtsy — free Etsy seller tools

Most-favorited Etsy listings for a search

etsy_most_favorited
Read-onlyIdempotent

Runs one Etsy search (first 100 active listings, relevance order) and ranks those listings by Etsy's own favorite count (num_favorers: the number of users who marked the listing a favorite), with title, link, price in the shop's currency and the year listed. Favorites are not sales: Etsy does not publish sales per listing, so this is not a best-seller list. Use for 'what do shoppers favorite on Etsy for ?' and product-idea research.

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": {
      "query": "<query>"
    },
    "name": "etsy_most_favorited"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesProduct phrase, e.g. 'ceramic mug'
physicalNoDrop digital downloads/patterns from the results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds real behavioral context beyond them: the search is capped at the first 100 active listings, results are drawn in relevance order, and the ranking is by favorite count rather than sales. The explicit caveat that favorites are not sales and that Etsy does not publish per-listing sales prevents a serious misinterpretation of the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three sentences, front-loaded with what the tool does, then the caveat, then the use case. The parenthetical defining num_favorers is justified, but the quoted-phrase usage example and the sales disclaimer could be tightened slightly without losing meaning.

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

Completeness5/5

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

There is no output schema, so the description compensates by enumerating returned fields (title, link, price with currency, year listed). Combined with the 100-listing scope and relevance-ordering note, an agent has everything needed to call this correctly and to interpret the results without overreach.

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 (query, physical) are already documented in the schema and the baseline of 3 applies. The description adds no guidance on the physical flag or query phrasing, though it does clarify output semantics (price in shop currency, year listed) that go beyond input parameters.

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 chain (runs one search, then ranks) on a specific resource (Etsy active listings) and names the ranking key (num_favorers). It also explicitly delimits the tool against adjacent concepts by saying it is not a best-seller list, which lets an agent distinguish it from sales/rank siblings without opening schemas.

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?

Gives an explicit use case with a quoted query pattern ('what do shoppers favorite on Etsy for <product>?') plus product-idea research, and rules out the sales-interpretation misuse. It stops short of naming the sibling tools (etsy_shop_sales, etsy_rank_check) that an agent should pick instead when it actually wants sales or ranking data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources