Skip to main content
Glama

my_listings

Read-onlyIdempotent

Seller: all your listings, paused ones included, with active and reports. Needs your key.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoyour key, if your client cannot send headers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "your key, if your client cannot send headers",
      +  "type": "string"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds seller scoping, paused inclusion, and the need for a key, but says nothing about pagination, ordering, or what 'reports' refers to.

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?

The definition is very short and front-loads 'Seller', with no obvious padding. The phrase 'with active and reports' is ambiguous, but the overall structure remains economical.

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 read-only tool with no required parameters, full schema coverage, and annotations, the description covers own-listing scope, paused inclusion, and authentication. Because there is no output schema, the vague 'active and reports' phrase leaves return content and format under-explained.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents api_key. The description only restates 'Needs your key' and adds no format or fallback semantics beyond the schema.

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?

States seller-scoped retrieval of all one's listings and explicitly includes paused ones, which distinguishes it from a general listing search. However, 'with active and reports' is unclear and leaves the exact content of the listing response partly vague.

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?

Signals use for retrieving all of a seller's own listings, including paused ones, but does not explicitly say when to prefer it over search_listings or get_listing, nor when not to use it.

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