Skip to main content
Glama
lumile

MercadoLibre MCP Server

by lumile

product_description

Retrieve product descriptions from MercadoLibre using product IDs to display detailed item information for listings or research.

Instructions

Obtiene la descripción de un producto

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
productIdNoID del producto

Implementation Reference

  • The handler case in callTool method for the 'product_description' tool. Extracts productId from args, calls apiService.productDescription, and returns the result as JSON text content.
    case 'product_description': {
      const { productId } = args as { productId: string }
      const description = await this.apiService.productDescription(productId)
      return {
        content: [{ type: 'text', text: JSON.stringify(description, null, 2) }]
      }
    }
  • Registration of the 'product_description' tool in the listTools method, including name, description, and input schema.
    {
      name: 'product_description',
      description: 'Obtiene la descripción de un producto',
      inputSchema: { type: 'object', properties: { productId: { type: 'string', description: 'ID del producto' } } }
    }
  • Input schema definition for the 'product_description' tool, requiring a productId string.
    {
      name: 'product_description',
      description: 'Obtiene la descripción de un producto',
      inputSchema: { type: 'object', properties: { productId: { type: 'string', description: 'ID del producto' } } }
    }
  • Helper method in ApiService that fetches the product description from the MercadoLibre API endpoint.
    async productDescription (productId: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${this.baseURL}items/${productId}/description`, { 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 action ('obtiene') but doesn't describe whether this is a read-only operation, requires authentication, has rate limits, or what the return format looks like. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence in Spanish that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero wasted text, making it highly concise and well-structured.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate but has clear gaps. It states what the tool does but lacks behavioral details, usage context, and output information. Without annotations or output schema, the description should provide more complete guidance for effective use.

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 schema description coverage is 100%, with the single parameter 'productId' documented in the schema as 'ID del producto'. The description doesn't add any additional meaning about parameters beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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?

The description 'Obtiene la descripción de un producto' clearly states the verb ('obtiene' - gets) and resource ('descripción de un producto' - product description), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'product_reviews' or 'seller_reputation', which would require mentioning it's specifically for retrieving descriptive information rather than reviews or seller data.

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 provides no guidance on when to use this tool versus alternatives like 'product_reviews' or 'seller_reputation'. It doesn't specify use cases, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone 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