Skip to main content
Glama
lumile

MercadoLibre MCP Server

by lumile

seller_reputation

Retrieve seller reputation scores on MercadoLibre to evaluate trustworthiness before purchasing. Input a seller ID to access detailed reputation metrics.

Instructions

Obtiene la reputación de un vendedor

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sellerIdNoID del vendedor

Implementation Reference

  • Handler case in callTool method that processes seller_reputation tool call by extracting sellerId and delegating to apiService.sellerReputation, then returning JSON-formatted response.
    case 'seller_reputation': {
      const { sellerId } = args as { sellerId: string }
      const reputation = await this.apiService.sellerReputation(sellerId)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(reputation, null, 2)
        }]
      }
    }
  • Input schema definition for the seller_reputation tool, specifying sellerId as required string.
    inputSchema: {
      type: 'object',
      properties: {
        sellerId: {
          type: 'string',
          description: 'ID del vendedor'
        }
      }
    }
  • Tool registration in listTools method, including name, description, and input schema.
    {
      name: 'seller_reputation',
      description: 'Obtiene la reputación de un vendedor',
      inputSchema: {
        type: 'object',
        properties: {
          sellerId: {
            type: 'string',
            description: 'ID del vendedor'
          }
        }
      }
    },
  • Core implementation in ApiService that fetches the seller's reputation data from MercadoLibre API endpoint /users/{sellerId}.
    async sellerReputation (sellerId: string) {
      const headers = await this.getHeaders()
      const response = await fetch(`${this.baseURL}users/${sellerId}`, { 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?

No annotations are provided, so the description carries the full burden. It states the tool 'obtains' reputation, implying a read operation, but doesn't disclose behavioral traits like whether it requires authentication, rate limits, error handling, or what the output format might be. For a tool with no annotations, 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. It's front-loaded with no wasted words, making it highly concise and well-structured for quick understanding.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'reputación' entails (e.g., numerical score, textual feedback), how results are returned, or any dependencies. For a tool with minimal structured data, the description should provide more context to be fully helpful.

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 the parameter 'sellerId' documented as 'ID del vendedor'. The description doesn't add any meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 reputación de un vendedor' clearly states the action (obtains) and resource (seller reputation) in Spanish. It's specific about what the tool does, though it doesn't differentiate from sibling tools like product_description or product_reviews, which focus on different resources. No tautology with the name 'seller_reputation'.

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. It doesn't mention sibling tools or any context for usage, such as prerequisites or scenarios where this tool is appropriate. This leaves the agent with minimal 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