Skip to main content
Glama
dan1d

mercadolibre-mcp

get_seller_info

Retrieve a seller's profile including reputation, ratings, and transaction statistics to assess trustworthiness before making a purchase.

Instructions

Get seller profile including reputation, ratings, and transaction stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seller_idYesSeller user ID

Implementation Reference

  • The actual handler function that executes the get_seller_info tool logic. It makes a GET request to the MercadoLibre API endpoint /users/{seller_id}.
    export async function getSellerInfo(
      client: MercadoLibreClient,
      params: GetSellerInfoParams
    ): Promise<unknown> {
      return client.get(`/users/${encodeURIComponent(String(params.seller_id))}`);
    }
  • Input schema/type definition for GetSellerInfoParams, requiring a single seller_id field of type number.
    export interface GetSellerInfoParams {
      seller_id: number;
    }
  • Registration of the get_seller_info tool in the MCP server using the McpServer.tool() method with Zod schema and handler.
    server.tool(
      "get_seller_info",
      "Get seller profile including reputation, ratings, and transaction stats.",
      {
        seller_id: z.number().describe("Seller user ID"),
      },
      async (params) => {
        try {
          const result = await tools.get_seller_info(params);
          return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
        } catch (error) {
          const message = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: message }], isError: true };
        }
      },
    );
  • Helper wiring in createMercadoLibreTools that binds the getSellerInfo action to the client instance, making it available as tools.get_seller_info.
    get_seller_info: (params: GetSellerInfoParams) => getSellerInfo(client, params),
    get_trends: (params?: GetTrendsParams) => getTrends(client, params),
Behavior4/5

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

No annotations provided, so description carries the burden. It discloses that the tool returns reputation, ratings, and transaction stats, which gives insight into output content. However, no mention of auth, rate limits, or idempotency; but for a simple getter it's acceptable.

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?

Single sentence, 11 words, front-loaded and to the point. No extraneous information.

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

Completeness4/5

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

Given the simplicity (one parameter, no output schema, no annotations), the description provides sufficient context: what it gets and what fields are included. Lacks mention of error handling or pagination, but those are not critical for this tool.

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?

Input schema fully covers parameter with description ('Seller user ID'). Description adds no extra semantic context beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

Description clearly states verb 'Get' and resource 'seller profile', specifying included data (reputation, ratings, transaction stats). Differentiates well from sibling tools that focus on categories, items, or trends.

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 guidance on when to use this tool versus alternatives. Lacks explicit exclusions or context for when another tool would be more appropriate.

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/dan1d/mercadolibre-mcp'

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