Skip to main content
Glama
lumile

MercadoLibre MCP Server

by lumile

product_reviews

Retrieve product reviews from MercadoLibre to analyze customer feedback and make informed purchasing decisions.

Instructions

Obtiene las reseñas de un producto

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdNoID del producto

Implementation Reference

  • Handler case for 'product_reviews' tool: extracts productId from args, calls apiService.productReviews, and returns JSON-stringified reviews as text content.
    case 'product_reviews': {
      const { productId } = args as { productId: string }
      const reviews = await this.apiService.productReviews(productId)
      return {
        content: [{ type: 'text', text: JSON.stringify(reviews, null, 2) }]
      }
  • Registration of the 'product_reviews' tool in listTools(), including name, description, and input schema requiring productId.
    {
      name: 'product_reviews',
      description: 'Obtiene las reseñas de un producto',
      inputSchema: {
        type: 'object',
        properties: {
          productId: { type: 'string', description: 'ID del producto' }
        }
      }
    },
  • Input schema for product_reviews tool: object with required productId string.
    inputSchema: {
      type: 'object',
      properties: {
        productId: { type: 'string', description: 'ID del producto' }
      }
    }
  • apiService.productReviews method: fetches product reviews from MercadoLibre API endpoint '/reviews/item/{productId}' using authenticated headers.
    async productReviews (productId: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${this.baseURL}reviews/item/${productId}`, { headers })
      if (!response.ok) {
        throw new Error(`HTTP error! status: ${response.status}`)
      }
      const data = await response.json()
      return data
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool obtains reviews but doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, error handling, or what the return format looks like (e.g., list, summary, ratings). This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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?

The description is a single, clear sentence in Spanish ('Obtiene las reseñas de un producto') that directly states the tool's purpose without unnecessary words. It's front-loaded and efficient, making it easy to parse quickly, which is ideal for conciseness in tool descriptions.

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

Completeness2/5

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

Given the tool's complexity (simple read operation with one parameter) but lack of annotations and output schema, the description is incomplete. It doesn't explain what the reviews include (e.g., text, ratings, dates), how they're returned, or any behavioral aspects like pagination or errors. For a tool that likely returns data, more context is needed to use it effectively.

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?

The input schema has 100% description coverage, with 'productId' documented as 'ID del producto'. The description doesn't add any parameter semantics beyond this, such as format examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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?

The description 'Obtiene las reseñas de un producto' clearly states the action (obtains) and resource (product reviews), providing a basic understanding of the tool's function. However, it doesn't differentiate from sibling tools like 'product_description' or 'seller_reputation' beyond the obvious resource difference, lacking specificity about scope or format of the reviews obtained.

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?

The description offers no guidance on when to use this tool versus alternatives like 'product_description' or 'seller_reputation'. It doesn't specify prerequisites, context for usage, or exclusions, leaving the agent to infer usage based solely on the tool name and description without explicit direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lumile/mercadolibre-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server