Skip to main content
Glama

Adicionar item na Vitrine

add_showcase_item

Publica uma oferta na Vitrine do bot (página pública, visível para qualquer visitante). O "link_url" é convertido no link de afiliado do bot antes de salvar; se a conversão falhar, nada é salvo. A mesma oferta postada há pouco (mesmo link) é mesclada no item existente em vez de duplicar. Exige permissão de escrita (bot:write).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "link_url": "<link_url>"
    },
    "name": "add_showcase_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNoOpcional. Chamada curta, ex.: "SÓ HOJE COM FRETE GRÁTIS".
priceNoOpcional. Preço, ex.: "R$ 99,90".
titleYesTítulo do produto.
couponNoOpcional. Código do cupom.
destaqueNoOpcional. Destacar no início da Vitrine.
link_urlYesLink do produto ou o affiliate_url de search_products (https://...).
image_urlNoOpcional. Foto do produto (https://...).
old_priceNoOpcional. Preço de antes.
expires_atNoOpcional. Quando o item sai da página (data ISO ou epoch). Ausente = prazo padrão da Vitrine.

Output Schema

NameRequiredDescriptionDefault
itemNoO item salvo, com o link de afiliado mintado em link_url.
avisoNo
successNo
public_urlNoPágina pública da Vitrine; null se não está publicada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: link_url is rewritten into the bot's affiliate link before saving, failure of that conversion means nothing is persisted (all-or-nothing), recent duplicate links are merged into the existing item instead of creating a duplicate, and bot:write permission is required. These are exactly the traits an agent needs before mutating public state.

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?

Four tight sentences, front-loaded with what the tool does, then the risky side effects (conversion, atomicity, merging) and the permission requirement. No filler or restatement of schema fields.

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

Completeness4/5

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

A mutation tool with nine parameters, but annotations plus an output schema plus full schema coverage leave little for the description to carry, and it covers the important side effects. The one gap is merge precedence: it does not say whether the incoming fields overwrite or only fill missing fields on the existing item.

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 field-level meaning is already documented. The description adds real value on the key parameter by specifying that link_url is converted to an affiliate link and that it also governs the merge/dedup behavior — semantics not derivable from the schema.

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?

States a concrete verb and resource ("Publica uma oferta na Vitrine do bot") and clarifies the scope: a public page visible to any visitor. It does not explicitly contrast with adjacent write tools such as create_offer_post or propose_offer_post, so the agent must infer the boundary from the resource name alone.

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

Usage Guidelines3/5

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

Usage is implied by the scope (publishing an offer to the public showcase) and by the mention that link_url can come from search_products, but there is no explicit when-to-use/when-not statement or named alternative for creating offers or coupons. The agent can infer intent but is not routed.

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