Skip to main content
Glama

List inventory

loyverse_list_inventory

List inventory stock levels per variant and store from Loyverse with cursor pagination. Optionally fetch all pages automatically.

Instructions

List inventory from Loyverse (GET /inventory). Supports cursor pagination. List returns stock levels per variant/store. Update expects a body like { inventory_levels: [{ variant_id, store_id, stock_after }] }. Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoItems per page, Loyverse default 25, max 250.
queryNoExtra query string filters supported by this endpoint (e.g. store_id, updated_at_min, created_at_max).
cursorNoPagination cursor from a previous response.
fetch_allNoIf true, follows pagination automatically and returns every page combined (capped at 20 pages for safety). If false/omitted, returns a single page.
Behavior3/5

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

The description discloses pagination behavior (cursor, fetch_all auto-fetching up to 20 pages) and error handling (400 error returned verbatim). However, it fails to explicitly state that the operation is read-only, and includes irrelevant information about the update endpoint which detracts from transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise with five sentences, but the sentence about 'Update expects a body...' is irrelevant to the list operation, wasting space. The core information is front-loaded, but the extraneous detail reduces efficiency.

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 lack of an output schema and the presence of a nested query object, the description should provide more detail on the return structure beyond 'stock levels per variant/store'. It also fails to clarify that field names follow an external API, which is helpful but not fully informative. The inclusion of update info is misleading.

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 coverage is 100% with detailed descriptions for all four parameters. The description adds context about pagination and the fetch_all auto-fetch limit, but does not significantly enhance understanding beyond the schema for limit, query, and cursor.

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 'List inventory from Loyverse (GET /inventory)' and explains it returns stock levels per variant/store, making the verb and resource clear. However, it includes an off-topic sentence about the update endpoint, which may cause confusion and does not actively distinguish from sibling tools like loyverse_update_inventory.

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 mentions pagination options but provides no explicit guidance on when to use this tool versus alternatives such as loyverse_update_inventory or other list tools. There is no statement of prerequisites or exclusion criteria.

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/ogarciabrena/mcploy'

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