Skip to main content
Glama
mercadolivre-mcp

mercadolivre-mcp

by romualdoag

Reputação do vendedor

get_seller_profile

Retrieves a Mercado Livre seller's public profile by numeric ID, including nickname, reputation level, transaction total, and positive feedback.

Instructions

Perfil público do vendedor: nickname, nível, total de transações e avaliações positivas. Para achar o seller_id, abra qualquer anúncio dele com get_item.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seller_id": "<seller_id>"
    },
    "name": "get_seller_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
seller_idYesid numérico do vendedor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. Declaring it a 'public profile' implies a safe read and the field list previews the result shape, which matters since there is no output schema, but error behavior for an invalid seller_id and any rate limits are unstated.

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?

Two short sentences, zero filler, with the payload contents front-loaded and the prerequisite second. Efficient, though it could be tightened marginally.

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?

With no output schema and no annotations, the description compensates by listing the returned fields and the way to obtain the required id. Remaining gaps are minor: failure modes and whether the data is cached or live.

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% and the single parameter already documents itself as a numeric seller id, so the baseline is 3. The description's tip on deriving seller_id from get_item adds practical value but does not explain format constraints beyond the schema.

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?

Names a specific resource (public seller profile) and enumerates what it contains: nickname, level, transaction count, positive ratings. This clearly separates it from the listing/search siblings, though it never explicitly says 'not for X'.

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

Usage Guidelines4/5

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

Gives an actionable prerequisite workflow: to obtain seller_id, open any of the seller's listings with get_item. That is concrete usage guidance tied to a real blocker, but there are no exclusions or when-not-to-use conditions.

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