Skip to main content
Glama

Listar itens da Vitrine

list_showcase_items
Read-only

Itens da Vitrine do bot (a página pública de ofertas /v/), mais recentes primeiro, com id, título, link, preço, cupom, se está ativo e quando vence. Use para "o que tem na minha Vitrine" e para achar o id antes de remove_showcase_item. Datas em ISO com o fuso de Brasília. Com has_more true, repita com cursor = next_cursor (ou offset = next_offset).

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

Input Schema

NameRequiredDescriptionDefault
limitNoItens por página (1 a 100; padrão 20).
cursorNoO next_cursor da resposta anterior: a próxima página continua dele, lendo só os itens dela.
offsetNoQuantos itens pular (0 = início). Para a próxima página, prefira o cursor; ignorado quando há cursor.

Output Schema

NameRequiredDescriptionDefault
itensNoItens da Vitrine: id, title, link_url, price, coupon, active, expires_at.
totalNoQuantos casaram com o filtro (todas as páginas).
successNo
has_moreNotrue quando há mais itens depois desta página.
next_offsetNooffset da próxima página; null na última.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "O next_cursor da resposta anterior: a próxima página continua dele, lendo só os itens dela.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / offset / description
      Previous value: -"Quantos itens pular (0 = início). Para a próxima página, use o next_offset da resposta."New value: +"Quantos itens pular (0 = início). Para a próxima página, prefira o cursor; ignorado quando há cursor."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered; the description contributes the pagination loop behavior and the ordering guarantee (most recent first). It does not state result-size limits or empty-list behavior, which keeps it below a 5.

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?

Front-loaded with purpose and scope, then usage, then pagination mechanics; nearly every clause carries information. The parenthetical explaining the Vitrine URL is justified for disambiguation, though the paragraph is dense enough that bullet-style structure would read faster.

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

Completeness5/5

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

For a read-only list tool with an output schema, full schema coverage and annotations, this is complete: what it returns, ordering, date format, and how to page through results are all present. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds value beyond it by spelling out the pagination protocol: when has_more is true, repeat with cursor = next_cursor or offset = next_offset. It also note-level clarifies the date format (ISO, Brasília timezone) that the schema does not encode.

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?

States a specific verb and resource ('Itens da Vitrine do bot'), clarifies what the Vitrine is (the public offers page /v/<slug>), specifies ordering and the exact fields returned, and names the sibling remove_showcase_item that consumes the ids. An agent can distinguish it from the other list_* siblings without opening a schema.

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

Usage Guidelines4/5

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

Gives two concrete use cases, 'o que tem na minha Vitrine' and locating the id before remove_showcase_item, which is real routing guidance. It stops short of exclusions or of pointing at add_showcase_item / search_products as alternatives, so it is clear context without full when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources