Skip to main content
Glama
gustavossouza

MCP Mercado Livre

by gustavossouza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_item

Create and publish a new Mercado Livre listing by submitting title, category, price, stock, required attributes, and pictures; returns item ID, status, and permalink.

Instructions

Create and PUBLISH a new listing on Mercado Livre — this is a real write operation: the item becomes public (immediately or per account settings) and selling fees apply once it sells. Confirm the details with the user before calling. Recommended flow: (1) predict_category with the title to get category_id; (2) get_category_attributes on that category and fill every attribute marked required via the attributes parameter; (3) optionally get_listing_types/get_listing_prices to choose the listing type and estimate fees; (4) call create_item. The title is limited to 60 characters. If Meli rejects the payload with a validation error, the full error body is returned — read it, fix the offending fields (usually missing required attributes) and retry. Returns the created item id, status and permalink.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYesSale price in currency_id
titleYesListing title, max 60 characters
picturesNoImage URLs; Meli downloads them (pictures[].source). For local files, upload first with upload_picture
shippingNoShipping options object, e.g. {free_shipping: true, mode: 'me2'}
video_idNoId of a video previously uploaded to the seller's account
conditionNoItem condition: 'new' or 'used' (default 'new')new
attributesNoItem attributes; MUST include all attributes marked required by get_category_attributes
buying_modeNoBuying mode; keep 'buy_it_now' unless the user explicitly wants auctionbuy_it_now
category_idYesCategory id from predict_category, e.g. 'MLB1055'
currency_idNoISO currency of the price. Defaults to the site currency (BRL for MLB)
descriptionNoPlain-text listing description
listing_type_idNoExposure plan id from get_listing_types, e.g. 'gold_special' (Clássica, default) or 'gold_pro' (Premium)gold_special
available_quantityYesStock quantity available for sale

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full behavioral burden and does so: it discloses that the item becomes public, that selling fees apply, that user confirmation is required, how errors surface (full error body returned), and common remediation (missing required attributes). It also states return values (item id, status, permalink).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the critical fact (real write/public/fees) before the workflow, and the numbered steps are scannable. It is dense and slightly long, but nearly every clause carries actionable information.

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

Completeness5/5

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

For a 13-parameter mutation tool with nested objects, no annotations, and no output schema, the description supplies prerequisites, execution workflow, error semantics, and return values — everything needed to call it correctly.

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 description coverage is 100%, so the schema already documents all 13 parameters, including the 60-char title limit, attributes requirements, and listing_type_id origin. The description reinforces the workflow origins for category_id/attributes but adds little syntax beyond what the schema already states.

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?

States a specific verb (create and publish) on a specific resource (a listing on Mercado Livre), and immediately sets scope with 'this is a real write operation'. It is clearly distinguishable from siblings like update_item, update_item_status, and create_catalog_listing.

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

Usage Guidelines5/5

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

Provides an explicit numbered recommended flow naming alternatives (predict_category, get_category_attributes, get_listing_types/get_listing_prices) with the conditions that select each. Also states the confirm-with-user prerequisite and a retry procedure on validation failure.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools