Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

vinted_brands

Fetch Vinted's curated popular-brands directory and return each brand ID for direct use as the id parameter in brand lookup requests.

Instructions

Vinted popular-brands directory. Returns Vinted's "Popular brands" directory. This is Vinted's own curated list, not an exhaustive list of every brand in its catalog. Each entry's id is usable directly as the id query parameter to /vinted/brand. Public data, sourced from Vinted's own server-rendered brands page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description is the sole source. It discloses that the data is public and sourced from Vinted's server-rendered brands page, setting expectations for access and origin. It also notes the directory is curated and not exhaustive, which manages expectations about content coverage.

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 two sentences, front-loads the main purpose, and each clause adds distinct value (scope, ID usage, public data sourcing). No fluff.

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 no-parameter, no-output-schema read tool, the description covers the essential context: what it returns, scope limitations, and how results can be used downstream. It could specify entry fields beyond `id`, but that's a minor gap given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty with zero parameters, so there is nothing to document. The description appropriately avoids unnecessary parameter detail, and the mention of entry `id` usage is relevant to the return value rather than input parameters.

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 identifies the tool as returning Vinted's curated 'Popular brands' directory, with a specific verb ('Returns') and resource impact. It distinguishes itself from an exhaustive catalog by explicitly stating it's a curated subset, though it does not name an alternative sibling tool.

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?

It states this is Vinted's own curated list, implying it should be used when a user needs popular brands rather than the full catalog. It also provides specific downstream guidance that each entry's `id` can be used as the `id` query parameter to /vinted/brand, which helps an agent decide when to call this vs. related tools.

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