Skip to main content
Glama
Sign In
mercadolivre-mcp

mercadolivre-mcp

by romualdoag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Ficha do produto

get_product

Retrieves a complete Mercado Livre catalog product record—including attributes, photos, and variations—using a product ID.

Instructions

Ficha completa de um produto de catálogo (atributos, fotos, variações).

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": {
      "product_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesid do produto (ex. MLB52753326)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only lists returned content. It never states that this is a read-only lookup, what happens when product_id is unknown or invalid, or that a single record is returned.

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?

One short sentence, front-loaded with the resource and immediately followed by the concrete payload contents. Nothing is wasted, though the sentence is too minimal to route the agent among siblings.

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

Completeness3/5

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

For a single-parameter read tool with no output schema, the description at least tells the agent what comes back (attributes, photos, variations), which is the main thing schema cannot convey. The absence of any usage routing or error behavior leaves the definition only minimally adequate.

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 single product_id parameter is documented in the schema with an example id. The description adds no further meaning about the identifier format or scope, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Ficha completa de um produto de catálogo" names the resource and enumerates what the record contains (attributes, photos, variations), so the agent knows it retrieves full product detail. It does not distinguish this from close siblings such as get_item or search_products, and the action verb is only implied.

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?

No indication of when to use this versus search_products (lookup by query) or get_item (by item id), which is the main ambiguity an agent faces here. Usage is only inferable from the tool name.

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

Deploy Server

Other Tools