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

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_my_shop

Read-only

Retrieves your Etsy shop profile details, including name, URL, currency, counts, and reviews, so you can verify shop identity and status.

Instructions

Your Etsy shop: name, URL, currency, counts, reviews.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the only available disclosure of return content — name, URL, currency, counts, reviews — which matters because there is no output schema. It does not say what 'counts' or 'reviews' contain, so it is not fully transparent.

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?

Nine words, front-loaded with the resource and then the payload. Nothing is wasted, though the fragment style (no verb, colon-separated field list) reads more like a label than an instruction.

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

Completeness3/5

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

For a simple zero-parameter read tool this is close to sufficient, but with no output schema the vague terms 'counts' and 'reviews' are never resolved, and there is no note about behavior when no shop exists. An agent knows what it will get in general, not precisely.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object, so there is nothing to disambiguate. The description correctly implies no arguments are needed to scope the call.

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 phrase 'Your Etsy shop' plus an enumerated field list makes it clear this returns the authenticated seller's shop metadata, which no sibling (listings, receipts, profiles) covers. It lacks an explicit verb such as 'Get' or 'Returns', so it stops short of the 5 anchor.

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?

There is no when-to-use statement, no prerequisites (e.g. requires an authenticated seller account), and no mention of alternatives or failure cases when the account has no shop. The agent must infer the use case from the field list alone.

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