Skip to main content
Glama

Extract design tokens

extract_design_tokens
Read-only

Analyze Pinterest board images to generate a role-based color palette with WCAG contrast ratios, CSS variables, and Tailwind colors for matching UI design.

Instructions

Analyzes the images on a board (public board link, logged-in board id, or a list of pins) and returns a color palette with roles (background, surface, text, muted, accent), WCAG contrast ratios, CSS variables and a Tailwind colors snippet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_design_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorsNo
pin_idsNo
board_idNoBoard id from list_boards (needs login)
max_pinsNo
board_urlNoPublic board link; works without login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description goes beyond that by disclosing exactly what the analysis returns (role assignments, contrast ratios, CSS/Tailwind output). It omits cost/latency expectations for image analysis and any failure behavior for inaccessible boards, which keeps it from a 5.

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?

A single front-loaded sentence where the verb and the three accepted input forms come first and the return payload is enumerated compactly. Every clause adds information; there is no filler or restatement of the title.

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, the description correctly takes on the burden of describing return values and does so in detail, and it covers the three input modes. It still leaves the palette-size and pin-sampling parameters unexplained and does not say how conflicting input modes are resolved, so it is strong but not complete for a 5-parameter tool.

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 description coverage is only 40%, so the description should carry more weight; it does map its three input modes onto board_url, board_id, and pin_ids, but says nothing about the `colors` count (3–12) or `max_pins` sampling limit, which materially change the output. Partial compensation only.

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?

States a specific verb+resource (analyzes board images, extracts design tokens) and enumerates the concrete outputs: role-tagged color palette, WCAG contrast ratios, CSS variables, Tailwind snippet. Nothing among the siblings (pin/board retrieval, auth) could be confused with this, so an agent can select it on name+description alone.

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

Usage Guidelines3/5

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

The parenthetical input modes (public board link, logged-in board id, or a list of pins) imply the three calling contexts, which is useful routing information. However, it never states when to prefer this over simply fetching pins with get_board_pins, nor what to do if both a board and pin_ids are supplied, so usage is implied rather than explicit.

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