Skip to main content
Glama

Converter uma lista de produtos

convert_list
Read-only

Gera o link de afiliado de CADA produto de uma lista de afiliado do Mercado Livre (meli.la, /sec/ ou o link longo mercadolivre.com.br/social//lists/). Lê todas as páginas da lista e converte até "limit" produtos por chamada (padrão 100, até 150); se sobrar, a resposta traz next_start: chame de novo com start igual a ele. Por produto: title, price, original_price, image_url, product_url e final_url (o link a publicar). Anúncio fora do ar não aparece na lista, então pode haver menos produtos que o total dela. O convert_links só converte lista que tem um produto; para as outras, use esta.

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": {
      "url": "<url>"
    },
    "name": "convert_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLink da lista do Mercado Livre (meli.la, /sec/ ou /social/<perfil>/lists/<id>).
limitNoOpcional. Quantos produtos converter nesta chamada (padrão 100, até 150).
startNoOpcional. Posição do 1º produto a converter (0 = do começo). Use o next_start da resposta anterior.
telegram_user_idNoOpcional. ID do usuário do Telegram para tracking por usuário.

Output Schema

NameRequiredDescriptionDefault
listNoid, profile, name, url, total (quantos a lista diz ter), pages_read e pages_total.
itemsNoUm por produto desta fatia: title, price, original_price, image_url, product_url, final_url (o link a publicar) e, quando falhou, error.
startNo
failedNo
successNo
convertedNo
next_startNostart da próxima chamada; null quando esta chegou ao fim da lista.
products_foundNoProdutos à venda achados na lista, em todas as páginas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly/openWorld/non-destructive), it discloses real behavior: it reads every page, converts up to `limit` per call (max 150), returns next_start to resume, and notes that out-of-stock ads are absent so fewer products than the list total may be returned. These are substantive behavioral disclosures the annotations do not carry.

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?

Front-loaded with purpose, then pagination, return fields, out-of-stock caveat, and finally sibling routing. Every sentence carries information; the return-field sentence even clarifies that final_url is the link to publish, so little is wasted.

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?

An output schema exists, so the return-value details are bonus, not required; the description still clarifies final_url's role. For a 4-parameter read-only tool it covers purpose, pagination, routing, caveats, and output semantics completely.

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 description coverage is 100%, and the description largely restates the schema: limit defaults to 100 (max 150) and start resumes from next_start. The re-call pattern adds some value but does not introduce syntax or meaning the schema is missing, so the baseline 3 applies.

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?

Opens with a specific verb and resource ("Gera o link de afiliado de CADA produto de uma lista de afiliado do Mercado Livre"), defines the accepted URL formats, and explicitly distinguishes itself from the sibling convert_links. An agent can tell exactly what it produces without opening the schema.

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

Usage Guidelines5/5

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

States the routing rule explicitly: convert_links only handles single-product lists, so for other lists use this tool. It also specifies the pagination contract (call again with start equal to next_start when more products remain). Both when-to-use and how-to-continue are covered.

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