Fetch a Vinted seller's public profile and ratings, with optional recent reviews and listings to evaluate trust before buying or negotiating.
A member's public profile and ratings; optionally recent reviews and their listings.
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | ||
| include_items | No | ||
| include_reviews | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It says the profile is public and mentions optional reviews/listings, but does not disclose permissions, rate limits, error behavior, or whether the operation has side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence front-loads the main resource and then notes optional additions. No wasted text, though it is telegraphic to the point of leaving gaps.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, and 0% schema coverage, the description should do more. It does not explain the shape of the profile/ratings response, pagination, failure modes, or parameter details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It loosely maps 'member' to user_id, 'reviews' to include_reviews, and 'listings' to include_items, but does not clarify ID format, defaults, or what 'recent' means.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the resource: a member's public profile and ratings, with optional recent reviews and listings. It is specific about content but does not explicitly differentiate itself from siblings like seller_items or get_item.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies usage by describing optional data, but offers no explicit when-to-use guidance, prerequisites, or alternatives. An agent must infer when to call get_seller versus seller_items.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.