Skip to main content
Glama
dan1d

mercadolibre-mcp

get_item_description

Retrieve the full text description of any MercadoLibre item by providing its item ID. Access detailed product information for analysis or display.

Instructions

Get the full text description of a MercadoLibre item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesItem ID

Implementation Reference

  • The core handler function getItemDescription that performs a GET request to /items/{item_id}/description on the MercadoLibre API and returns the item description.
    export async function getItemDescription(
      client: MercadoLibreClient,
      params: GetItemDescriptionParams
    ): Promise<unknown> {
      return client.get(`/items/${encodeURIComponent(params.item_id)}/description`);
    }
  • Registration of 'get_item_description' as an MCP tool on the server with Zod schema for item_id input and error handling.
    server.tool(
      "get_item_description",
      "Get the full text description of a MercadoLibre item.",
      {
        item_id: z.string().describe("Item ID"),
      },
      async (params) => {
        try {
          const result = await tools.get_item_description(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 };
        }
      },
    );
  • src/index.ts:30-30 (registration)
    Registration of the tool name 'get_item_description' mapping to the getItemDescription handler with typed params.
    get_item_description: (params: GetItemDescriptionParams) => getItemDescription(client, params),
  • TypeScript interface GetItemDescriptionParams defining the input shape (item_id: string).
    export interface GetItemDescriptionParams {
      item_id: string;
    }
Behavior2/5

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

No annotations provided, and description does not disclose any behavioral traits such as read-only nature, authentication requirements, rate limits, or error behavior. Burden falls entirely on description due to missing annotations.

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, no wasted words, front-loaded with action. Highly concise.

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?

For a simple getter with one parameter and no output schema, description provides core functionality. Lacks error handling or output format details, but adequate for minimal 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?

Single parameter 'item_id' with schema description 'Item ID'. Description adds no further meaning. With 100% schema coverage, baseline 3 is justified.

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 states 'Get the full text description of a MercadoLibre item.' Uses specific verb 'Get' and resource 'full text description', clearly distinguishing from siblings like 'get_item' which returns all item details.

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?

No explicit guidance on when to use versus alternatives like 'get_item' or 'get_seller_info'. Usage is implied but not clarified with conditions or exclusions.

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