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

etsy-clean-mcp

by phobicdotno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

list_receipts

Read-only

Retrieve your Etsy shop orders (receipts) newest first, then filter by paid or shipped status and paginate results with limit and offset.

Instructions

Your orders (receipts), newest first. Filter by paid/shipped.

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": "list_receipts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
was_paidNo
was_shippedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one useful behavioral fact beyond that — results are ordered newest first — but says nothing about pagination behavior, defaults (limit 25/offset 0), or result size, which matter for a paged list tool.

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 tight sentences with the resource and ordering front-loaded and the filter capability stated second. No filler or redundancy.

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 simple read-only listing tool with no output schema and no required parameters, the description covers purpose, ordering, and filtering adequately. The remaining gap is pagination semantics for limit/offset, which is a modest omission rather than a blocking one.

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 0%, so the description must carry parameter meaning. It explains two of four parameters semantically (paid/shipped map to was_paid/was_shipped), but limit and offset are left entirely undocumented in both places. Partial compensation only.

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 states the resource ('Your orders (receipts)') and the ordering ('newest first'), which makes the plural list nature clear and distinguishes it from get_receipt for a single record. It stops short of naming siblings or explicitly contrasting the list vs. single-record tools, so it is clear but not fully differentiated.

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?

'Filter by paid/shipped' implies the intended use case of narrowing the list, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as get_receipt. Usage is only implied.

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