Skip to main content
Glama
shoper-mcp

shoper-mcp

by exelmedia

Producenci / List producers

list_producers
Read-onlyIdempotent

Retrieve a paginated list of store producers (brands), optionally filtered by a name fragment, to browse or find brands in a Shoper catalog.

Instructions

PL: Lista producentów (marek) sklepu, opcjonalnie po fragmencie nazwy. Maks. 50 na stronę. EN: Paginated list of producers (brands), optionally filtered by name fragment.

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

Input Schema

NameRequiredDescriptionDefault
pageNoNumer strony od 1 / page number, starting at 1
limitNoLiczba wyników na stronę (1-50) / page size
queryNoFragment nazwy / name fragment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds a useful behavioral fact — a hard cap of 50 results per page — but says nothing about result ordering, total counts, or what happens when the query matches nothing.

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?

Two compact sentences with the core purpose front-loaded in the Polish and English versions. The bilingual duplication doubles the length, but each version is otherwise free of filler.

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 three-parameter, read-only list tool with full schema coverage and no output schema, the description covers purpose, filtering and the page-size limit adequately. Only the shape/ordering of returned records is left implicit, which is a minor gap.

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 100%, with page, limit and query all documented in the schema including ranges and defaults. The description only echoes the pagination cap and the name-fragment filter, adding no syntax or matching semantics (e.g., case sensitivity, substring vs prefix) beyond what the schema provides.

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 a specific verb and resource ("paginated list of producers (brands)") plus the optional name-fragment filter, so an agent knows exactly what the tool returns. It does not differentiate itself from siblings such as list_categories or search_products, which keeps it short of a 5.

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?

Usage is implied: the tool lists brands, optionally narrowed by a name fragment. There is no explicit statement of when to prefer this over search_products or when it is inappropriate, and no prerequisites mentioned, so guidance stays at the minimum-viable level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.