Skip to main content
Glama
Sign In
depix-mcp

depix-mcp

Official
by depixapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List products

list_products
Read-only

List products with flexible filtering by active flag or text search over name, slug, and description, with pagination via limit and offset.

Instructions

List products with filters and pagination. Requires scope merchant_read.

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

Input Schema

NameRequiredDescriptionDefault
qNoSubstring search over slug, name and description.
limitNo
activeNoFilter by active flag.
offsetNo

Output Schema

NameRequiredDescriptionDefault
limitYes
offsetYes
has_moreYes
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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. The description adds the authorization requirement (scope merchant_read) beyond annotations. No contradictions are present. The description moderately enhances behavioral context.

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?

The description is extremely concise: two sentences with no superfluous information. It front-loads the core purpose and includes the scope requirement efficiently.

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?

Given the tool's simplicity (4 parameters, output schema exists), the description adequately covers the main behavior. It omits pagination details like limit defaults and offset usage, but the schema covers these. The scope requirement is the main extra context.

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 50% (2 of 4 parameters have descriptions). The description generically mentions 'filters and pagination' but does not elaborate on parameter details beyond what the schema provides. The baseline is 3 given the coverage level, and the description adds no extra semantic value.

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 clearly states 'List products with filters and pagination', specifying the verb (list), resource (products), and distinct features (filters and pagination). It differentiates from sibling tools like list_checkouts and list_product_checkouts by focusing on products.

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?

The description mentions 'Requires scope merchant_read', which provides authorization context. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. Usage is implied but not fully elaborated.

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