mercadolibre-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERCADOLIBRE_ACCESS_TOKEN | No | Optional access token for MercadoLibre API authentication (e.g., APP_USR-...). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_itemsB | Search products on MercadoLibre by keyword. Supports filtering by category, price range, and site (MLA=Argentina, MLB=Brazil, MLM=Mexico, etc.) |
| get_itemA | Get full details of a MercadoLibre item including title, price, pictures, seller, condition, and stock. |
| get_item_descriptionA | Get the full text description of a MercadoLibre item. |
| get_categoriesB | List all top-level categories for a MercadoLibre site. |
| get_categoryA | Get category details including name, path from root, and children categories. |
| get_seller_infoA | Get seller profile including reputation, ratings, and transaction stats. |
| get_trendsA | Get current trending searches on MercadoLibre for a specific site/country. |
| get_currency_conversionB | Convert between currencies using MercadoLibre exchange rates (ARS, BRL, MXN, USD, etc.). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: categories (list vs detail), items (full vs description), search, currency conversion, seller info, and trends. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern with snake_case, mostly using 'get_' prefix ('get_categories', 'get_item', etc.) except 'search_items' which still follows the verb_noun pattern. Very predictable.
8 tools is well within the ideal 3-15 range. The set covers all essential read operations for a marketplace data API without being too sparse or bloated.
The tool surface covers browsing categories, searching/filtering items, retrieving item details and descriptions, seller info, trends, and currency conversion. No obvious gaps for a read-only marketplace data API.