Skip to main content
Glama

GetProductCategories

Retrieve product categories from Medusa with filtering, sorting, and pagination options to organize e-commerce inventory.

Instructions

Retrieve a list of product categories. The product categories can be filtered by fields such as id. The product categories can also be sorted or paginated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNo
offsetNo
limitNo
orderNo
qNo
idNo
descriptionNo
handleNo
parent_category_idNo
include_ancestors_treeNo
include_descendants_treeNo
created_atNo
updated_atNo
$andNo
$orNo
nameNo
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions filtering, sorting, and pagination, but lacks details on permissions, rate limits, response format, or error handling. This is insufficient for a tool with 16 parameters and complex filtering options.

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 description is brief and front-loaded with the main purpose, using three sentences efficiently. However, it could be more structured by explicitly listing key parameters or use cases, but it avoids unnecessary verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (16 parameters, nested objects, no output schema), the description is incomplete. It doesn't explain the return values, error scenarios, or detailed behavioral traits, making it inadequate for effective tool invocation in this context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 compensate. It only vaguely mentions filtering by 'id' and other fields, sorting, and pagination, without explaining the 16 parameters' purposes, formats, or relationships. This leaves most parameters undocumented and unclear.

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 clearly states the verb ('Retrieve') and resource ('product categories'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'GetProductCategoriesId' or 'GetProducts', which also retrieve related data, so it lacks specific sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'GetProductCategoriesId' for a single category or 'GetProducts' for products. The description mentions filtering and sorting but doesn't specify contexts or exclusions for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SGFGOV/medusa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server