Skip to main content
Glama

My listings

list_my_listings
Read-onlyIdempotent

A seller's products or a designer's designs, newest first, with status and price. For a product, storefront_published says whether it is shown on the storefront, which is what pause_listing and resume_listing change. Page with starting_after set to next_cursor. Needs a connected Printlooper account.

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_my_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
starting_afterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: result ordering (newest first), the presence of status and price, the meaning of storefront_published, and the auth requirement. Missing are rate-limit or result-size behavior, but the value added on top of annotations is substantial.

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 tight sentences with no filler, front-loaded with what is returned and in what order before moving to field meaning, paging, and the auth prerequisite. The clause "which is what pause_listing and resume_listing change" is dense but earns its place by tying the field to the mutation siblings.

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 read-only, two-parameter listing tool with no output schema, the description supplies the essentials: ordering, the notable returned fields (status, price, storefront_published), pagination mechanics, and the account prerequisite. The remaining gap is the limit parameter's default/cap and any sense of total result count, which is minor for a paged list endpoint.

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 starting_after well (set it to next_cursor to page), but says nothing about limit, whose default of 20 and cap of 50 are only visible as bare schema constraints. Half the parameters are semantically covered, which is minimum-viable rather than strong.

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 names the resource concretely ("a seller's products or a designer's designs") and adds scope details the name doesn't carry: newest-first ordering and inclusion of status and price. It is distinguishable from siblings like pause_listing and resume_listing, which are explicitly framed as mutating the storefront_published field this tool reports. It stops short of an explicit verb ("list"), but the resource and framing are unambiguous.

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?

It gives a concrete prerequisite ("Needs a connected Printlooper account") and explains the relationship to pause_listing/resume_listing, so an agent knows this is the read side of that pair. Pagination instructions ("Page with starting_after set to next_cursor") tell the agent how to iterate. It offers no explicit exclusion or comparison against read alternatives such as get_design, so it falls short of a 5.

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