Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Seller list listings

seller_list_listings
Read-onlyIdempotent

List a seller's product listings page by page, including archived and flagged items. Filter for active listings to view live stock, price, and moderation flags.

Instructions

List the bound seller's product listings, paginated. Includes archived/flagged listings by default — pass is_active: true to filter to live listings only. Returns slug, category, stock, price, and any moderation flags.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_size": "<page_size>"
    },
    "name": "seller_list_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor from the previous page's next_cursor.
is_activeNoFilter by active status; omit to include archived listings too.
page_sizeYesResults per page (1-100, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds meaningful context beyond that: the default inclusion of archived/flagged listings and the behavior of the is_active filter, plus expected output fields. No contradictions with annotations.

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?

Three concise sentences with zero redundant phrasing. The main purpose is front-loaded, followed by key behavioral details and output expectations. Every sentence contributes value.

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 paginated list tool, the description covers default behavior, filtering, and output fields. The schema handles cursor and page_size definitions. It doesn't explicitly mention the response structure (e.g., next_cursor), but given no output schema and typical API conventions, the definition is complete enough for correct invocation.

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 coverage is 100%, so all three parameters are documented in the schema. The description echoes the is_active filter's effect, but the schema already states it. No additional semantic meaning is provided beyond what's already in the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('List') and resource ('the bound seller's product listings') along with pagination, clearly distinguishing it from sibling operations like seller_get_listing. It also specifies default inclusion of archived/flagged listings, making the scope 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?

The description implies when to use it (listing all product listings for the bound seller) and naturally separates from siblings by scope (multiple vs single). However, it does not explicitly mention alternatives like seller_get_listing for a single listing, so it stops short of full exclusions.

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