Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vinted_catalog

Search Vinted resale listings by text and filter by price range or sort order to find secondhand items that match your query.

Instructions

Vinted listing search. Returns Vinted resale listings matching a text search, with optional price filtering and sort order. order values: relevance, newest_first, price_high_to_low, price_low_to_high. Public data, sourced from Vinted's own server-rendered catalog page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1
orderNoSort order. Allowed values: relevance, newest_first, price_high_to_low, price_low_to_high
price_toNoMaximum price
price_fromNoMinimum price
search_textYesSearch text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / order / enum
      Added value: +[
+  "relevance",
+  "newest_first",
+  "price_high_to_low",
+  "price_low_to_high"
+]
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description must disclose behavior. It notes 'Public data, sourced from Vinted's own server-rendered catalog page,' which indicates no auth and a reliable source. However, it doesn't mention pagination behavior, rate limits, or the structure of returned listings. This is a modest contribution beyond the schema but not comprehensive.

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?

The description is a single concise sentence with a separate note for order values and source. It's front-loaded with the core purpose, and every element serves a purpose. No fluff or redundancy.

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

Completeness3/5

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

For a search tool with five parameters and no output schema, the description covers the search functionality, filters, sort options, and data source. It doesn't describe the response format or pagination details, which could be important for an agent. It's adequate but leaves gaps.

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%, so all parameters are documented. The description repeats the order enum values and mentions 'optional price filtering,' which adds minimal context. Since the schema already explains parameters, the description adds little new semantic meaning, keeping it at the baseline for high coverage.

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?

The description clearly states the tool performs a search for Vinted resale listings, with a specific verb ('search') and resource ('Vinted listing'). It mentions optional filters and sort order, which differentiates it from item/member tools. It doesn't explicitly name sibling tools but the name and scope make it distinct.

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?

The description implies usage: search for Vinted listings by text with optional price/sort filters. It provides clear context for when to use it, but doesn't explicitly state when not to use it or mention alternatives like vinted_item for specific items. The context is adequate but not exhaustive.

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