Skip to main content
Glama

etsy_search_shops

Search for Etsy shops by name using an API key. Paginate results with limit and offset.

Instructions

Search for Etsy shops by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYes
shop_nameYesShop name to search for
limitNo
offsetNo
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only mentions searching by name, ignoring authentication (api_key), pagination (limit/offset), response format, rate limits, or whether results are exact matches or fuzzy. This is insufficient for a search tool.

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 a single concise sentence, which is efficient. However, it omits critical information, making it under-specified rather than appropriately brief. It could be improved with more structure without losing conciseness.

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 no annotations, no output schema, and 4 parameters with only 25% schema coverage, the description is incomplete. It lacks return value description, prerequisites, and any behavioral context necessary for a search tool.

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

Parameters2/5

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

Schema description coverage is only 25% (only 'shop_name' has a description). The description adds no parameter details beyond 'by name', leaving 'api_key', 'limit', and 'offset' unexplained. The low coverage requires compensation, which is absent.

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 clearly states 'Search for Etsy shops by name,' specifying the verb (search) and resource (shops). However, it doesn't differentiate from sibling tools like 'etsy_search_listings' or 'etsy_get_shop', which have distinct purposes.

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 provides no guidance on when to use this tool versus alternatives (e.g., 'etsy_get_shop' for a known shop). There are no explicit contexts, exclusions, or references to other tools.

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/malamutemayhem/unclick'

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