TimeLib MCP

list_collections

Search and paginate product collections in a Medusa v2 store, with optional field selection and results limits to control response size.

Instructions

List product collections.

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

Input Schema

Name	Required	Description
`q`	No
`limit`	No	Max results (default 20).
`fields`	No	Comma-separated field selection, e.g. 'id,title,status,*variants'. Use to keep responses small.
`offset`	No	Results to skip (pagination).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 4, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It fails to disclose whether this is a read-only operation, whether pagination is required for large datasets, default behaviors, or what the response contains. For a list operation this is a notable gap, though 'list' implies read-only nature.

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?

Extremely concise single sentence with no wasted words. However, it borders on under-specification rather than efficient conciseness, slightly reducing the score.

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?

With no output schema, no annotations, and a vague one-line description, this tool is under-documented. The schema does cover most parameters, but there's no info about return values, pagination behavior, or potential edge cases. This is a basic listing tool with minimal context for the agent.

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 75%, with limit, fields, and offset already documented in the schema. The description adds nothing about the 'q' parameter (which appears to be the undocumented 25%). No additional meaning is provided beyond the schema.

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

Purpose3/5

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

The description states 'List product collections' which names the verb (list) and resource (product collections). However, it lacks specificity about scope (all collections? published only?) and doesn't distinguish from siblings like list_categories, list_products, or list_product_tags beyond the resource name.

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 on when to use this tool vs alternatives. There's no mention of context or when listing collections would be preferred over other list tools. The description is too brief to convey usage context.

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