List seller listing IDs and paginate large inventories with scan and scroll_id, enabling access beyond 1,000 results.
Lista IDs de publicaciones del vendedor; scan y scroll_id permiten recorrer más de 1000.
| Name | Required | Description | Default |
|---|---|---|---|
| scan | No | ||
| limit | No | ||
| offset | No | ||
| status | No | ||
| scroll_id | No | ||
| seller_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, non-destructive, open-world behavior. The description adds useful behavioral context by explaining that scan and scroll_id enable traversal beyond 1000 results, which is not captured in the annotations or schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact sentence with the core purpose and pagination caveat front-loaded. There is no redundant or filler text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
It adequately identifies the return as a list of IDs and explains deep pagination, which are key aspects of the tool. However, with no output schema and 0% schema description coverage, the description should do more to clarify the non-pagination parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry parameter meaning. It explains scan and scroll_id for deep pagination but leaves seller_id, limit, offset, and status undocumented, which is a significant gap for a six-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it lists seller publication IDs, which distinguishes it from sibling tools that fetch item details. It does not explicitly name alternatives, but the purpose is clear enough for an agent to identify the operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for paginated listing when more than 1000 items are needed via scan and scroll_id. However, it does not state when to use this tool instead of meli_get_items or meli_search_catalog, nor does it provide exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.