Skip to main content
Glama
inkeedecoder-mcp

inkeedecoder-mcp

by knorby

Get a product

inkeedecoder_get_product
Read-onlyIdempotent

Fetch a cosmetic product page by slug, path, or INKEEDecoder/INCIDecoder URL to get brand, description, and full ingredient list, plus optional grouped functions, irritancy data, and tooltips.

Instructions

Fetch a cosmetic product page from INKEEDecoder (formerly INCIDecoder): brand, description, and full ingredient list, plus optional sections you opt into (grouped-by-function ingredients, irritancy/comedogenicity table, tooltips, long ingredient writeups). Accepts a slug, a /products/ path, or an inkeedecoder.com or incidecoder.com URL. Returns one page of data — verbose sections are off by default. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesProduct slug, site path (/products/...), or product URL on inkeedecoder.com or incidecoder.com. The slug is the last segment of the page URL. Get one from inkeedecoder_search.
brandNoInclude the brand name and its /brands/ link. Default true.
datesNoInclude who uploaded the product and when it was last updated. Default false.
imagesNo`none` omits images; `original` (default) includes the main image; `all` adds the webp/jpeg srcset URLs.original
hashtagsNoInclude the product's hashtags (#alcohol-free and similar). Default true.
tooltipsNoInclude per-ingredient tooltip data (functions, irritancy, comedogenicity, blurb). Default false.
full_nameNoInclude the canonical "Brand Product" full name. Default false.
functionsNoInclude ingredients grouped by what they do (key and other groups). Default false.
skim_tableNoInclude the per-ingredient irritancy/comedogenicity table. Default false — it is large.
descriptionNoInclude the product description. Default true.
ingredientsNoInclude the deduplicated ingredient list in INCI order. Default true.
long_descriptionsNoInclude the long per-ingredient writeups from "Ingredients explained". Default false — this is by far the largest section.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
pathYes
slugYes
brandNo
datesNo
imagesNo
fullNameNo
hashtagsNo
tooltipsNo
functionsNo
skimTableNo
descriptionNo
ingredientsNoDeduped ingredient list in INCI order.
longDescriptionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, and the description's 'Read-only' merely echoes that. What it adds beyond the annotations is meaningful: results are 'one page of data' (no pagination), and verbose sections default to off, which shapes how the agent should call it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb, resource, and returned payload, followed by accepted input formats and a note on verbosity defaults. Dense but readable; the parenthetical section list is long yet functional, and no sentence is filler.

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 an output schema present and annotations covering the safety profile, the description doesn't need to explain return values. It covers input flexibility (slug, path, URL), default verbosity, and single-page scope, which is enough for a 12-parameter tool. Only the lack of routing guidance to sibling tools keeps it short of a 5.

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% and every parameter carries its own description and defaults, so the description's summary of optional sections is largely a restatement. It adds no syntax or format detail for the polymorphic 'id' parameter beyond what the schema already documents. Baseline 3 applies.

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 and resource ('Fetch a cosmetic product page from INKEEDecoder') and enumerates what comes back (brand, description, full ingredient list) plus the opt-in sections. This is clearly distinct from the sibling tools that fetch brands, ingredients, or ingredient functions.

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?

Usage context is implied rather than stated: it explains that verbose sections are off by default and must be opted into, which guides invocation style. But it never says when to prefer this over inkeedecoder_get_ingredient or inkeedecoder_search_products, and the pointer to inkeedecoder_search for obtaining a slug lives only in the schema.

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