Skip to main content
Glama
googlarz

Vinted MCP and CLI Server

get_colors

Retrieve all Vinted color options with IDs, names, and hex codes. Use the IDs to filter search results by specific colors.

Instructions

Fetch the complete list of Vinted color options available as search filters. Returns every color with its numeric ID, display name, hex color code, short code (e.g. "BLACK"), and sort order. Pass the returned IDs to search_items.colorIds or search_all_items.colorIds to restrict results to specific colors. Results are cached for 1 hour — color catalogues change rarely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoVinted country site to query (color catalogues are shared across countries)fr

Implementation Reference

  • src/mcp.ts:160-168 (registration)
    Tool registration for 'get_colors' in the TOOLS array with name, description, and inputSchema (only optional 'country' parameter).
      name: 'get_colors',
      description: 'Fetch the complete list of Vinted color options available as search filters. Returns every color with its numeric ID, display name, hex color code, short code (e.g. "BLACK"), and sort order. Pass the returned IDs to search_items.colorIds or search_all_items.colorIds to restrict results to specific colors. Results are cached for 1 hour — color catalogues change rarely.',
      inputSchema: {
        type: 'object',
        properties: {
          country: { type: 'string', enum: COUNTRIES, default: 'fr', description: 'Vinted country site to query (color catalogues are shared across countries)' },
        },
      },
    },
  • src/mcp.ts:236-236 (registration)
    Switch-case handler in CallToolRequestSchema routing the tool name 'get_colors' to the opGetColors function.
    case 'get_colors': result = await opGetColors(c, a as any); break;
  • src/mcp.ts:17-17 (registration)
    Import statement importing opGetColors from src/ops/get-colors.js.
    import { opGetColors } from './ops/get-colors.js';
  • Handler function opGetColors that calls the underlying getColors API endpoint, defaulting country to 'fr'.
    export async function opGetColors(
      client: VintedClient,
      args: { country?: Country },
    ): Promise<ColorHit[]> {
      return getColors(client, args.country ?? 'fr');
    }
  • The ColorHit interface (id, title, hex, code, order) and the getColors client function that calls Vinted's /api/v2/colors API with 1-hour cache TTL and maps results.
    export interface ColorHit {
      id: number;
      title: string;
      hex: string;
      code: string;
      order: number;
    }
    
    export async function getColors(
      client: VintedClient,
      country: Country = 'fr',
    ): Promise<ColorHit[]> {
      const data = await client.apiGet<{ colors?: any[] }>(country, `/api/v2/colors`, STATIC_TTL_MS);
      return (data.colors ?? []).map((c) => ({
        id: Number(c.id),
        title: String(c.title ?? ''),
        hex: String(c.hex ?? ''),
        code: String(c.code ?? ''),
        order: Number(c.order ?? 0),
      }));
    }
Behavior5/5

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

With no annotations provided, the description fully carries the burden. It discloses that results are cached for 1 hour and color catalogues change rarely, and describes the exact return fields (numeric ID, display name, hex code, short code, sort order).

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 four sentences, each earning its place: purpose, output details, usage, caching policy. No filler, well front-loaded.

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 simple fetch tool with one parameter and no output schema, the description fully covers purpose, output structure, usage guidance, and caching behavior. It leaves no 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% for the only parameter (country), so baseline is 3. The description does not add new detail beyond what the schema already provides about the country parameter; it only restates shared-country info from the schema.

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?

The description clearly states 'Fetch the complete list of Vinted color options' with a specific verb and resource, and it distinguishes itself from sibling tools like get_categories or get_size_groups by focusing exclusively on color data.

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 explicitly tells users to pass the returned IDs to search_items.colorIds or search_all_items.colorIds, showing when to use this tool vs others. It also mentions caching behavior but does not include explicit when-not-to-use statements.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/vinted-mcp-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server