Skip to main content
Glama
dan1d

mercadolibre-mcp

get_item

Retrieve comprehensive details for a MercadoLibre item, including price, pictures, seller info, condition, and stock.

Instructions

Get full details of a MercadoLibre item including title, price, pictures, seller, condition, and stock.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesItem ID (e.g. MLA1234567890)

Implementation Reference

  • Core handler: calls MercadoLibre API GET /items/{item_id} to fetch item details.
    export async function getItem(
      client: MercadoLibreClient,
      params: GetItemParams
    ): Promise<unknown> {
      return client.get(`/items/${encodeURIComponent(params.item_id)}`);
    }
  • Input schema: expects a string item_id parameter.
    export interface GetItemParams {
      item_id: string;
    }
  • Registration: MCP tool registration with Zod schema validation and error handling.
    server.tool(
      "get_item",
      "Get full details of a MercadoLibre item including title, price, pictures, seller, condition, and stock.",
      {
        item_id: z.string().describe("Item ID (e.g. MLA1234567890)"),
      },
      async (params) => {
        try {
          const result = await tools.get_item(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 bridge: wraps the getItem action with a client and exposes it as get_item in the tools object.
      return {
        tools: {
          search_items: (params: SearchItemsParams) => searchItems(client, params),
          get_item: (params: GetItemParams) => getItem(client, params),
          get_item_description: (params: GetItemDescriptionParams) => getItemDescription(client, params),
          get_categories: (params?: GetCategoriesParams) => getCategories(client, params),
          get_category: (params: GetCategoryParams) => getCategory(client, params),
          get_seller_info: (params: GetSellerInfoParams) => getSellerInfo(client, params),
          get_trends: (params?: GetTrendsParams) => getTrends(client, params),
          get_currency_conversion: (params: GetCurrencyConversionParams) => getCurrencyConversion(client, params),
        },
      };
    }
Behavior3/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 describes a read operation but does not explicitly state it is read-only, mention authentication, or other behavioral traits. For a simple get, it is minimally sufficient.

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?

A single, clear sentence that front-loads the purpose and lists key fields. No wasted words.

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 simple single-parameter tool and no output schema, the description adequately covers the purpose and key fields. It could mention the output format (JSON) but is otherwise complete.

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?

Schema coverage is 100% with item_id described with an example. The description adds no additional meaning for the parameter beyond what the schema already provides.

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?

The description clearly states it retrieves full MercadoLibre item details and lists specific fields (title, price, pictures, etc.), distinguishing it from siblings like get_item_description and get_seller_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when full item details are needed, but lacks explicit when-to-use, when-not-to-use, or alternative tools. The sibling list provides context but the description itself offers no guidance.

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