paystack-mcp

list_products

Retrieve a paginated list of products from your Paystack account. Filter by date range to find products created within a specific period.

Instructions

List products available on your Paystack integration with pagination support

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

Name	Required	Description
`to`	No	A timestamp at which to stop listing product e.g. 2016-09-24T00:00:05.000Z
`from`	No	A timestamp from which to start listing product e.g. 2016-09-24T00:00:05.000Z
`page`	No	The page number to retrieve. Default is 1
`perPage`	No	Number of records to retrieve per page. If not specified we use a default value of 50

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

There are no annotations provided, so the description must carry the full burden of behavioral disclosure. It does not state whether the operation is read-only, what authentication is required, or any rate limits. Beyond 'List', it provides no additional 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?

Single, front-loaded sentence that states the action and key feature (pagination). Every word earns its place; no filler.

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

Completeness3/5

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

The description is adequate for a simple listing operation, but the absence of annotations and output schema means there is no disclosure of response format, authentication requirements, or error handling. It could be improved with a note about expected return values or prerequisites.

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?

All four parameters (to, from, page, perPage) have descriptions in the schema, so schema coverage is 100%. The description's mention of 'pagination support' aligns with page/perPage but adds no new meaning beyond what the schema already explains.

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 uses a specific verb 'List' with a clear resource 'products' and context 'Paystack integration'. It distinguishes from sibling tools like create_product and get_product by indicating this is the listing operation. The addition of 'pagination support' clarifies the scope.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives like get_product for single product retrieval. It mentions pagination support, implying it's for listing multiple products, but there is no explicit 'when not to use' or comparison to sibling tools.

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