makeup.land
Server Details
Israeli cosmetics retailer: ΔE shade matching, customer wallet, cart, orders, gift cards.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.8/5 across 8 of 8 tools scored. Lowest: 2.9/5.
Each tool targets a distinct resource or action (cart, customer, deals, brands, orders, payment links, products, gift cards), with no overlapping functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_cart, list_products, validate_gift_card), making the API predictable.
Eight tools cover a reasonable scope for a makeup loyalty server, focusing on queries for customer data, products, orders, and gift cards without being excessive or minimal.
The server lacks mutation tools (add to cart, create order, update customer) necessary for a full e-commerce workflow, leaving agents unable to perform essential actions beyond reading data.
Available Tools
8 toolsget_cartFetch a customer's cartInspect
Return the customer's most-recently-updated cart with per-line and total reward projection. Bearer + phone required.
| Name | Required | Description | Default |
|---|---|---|---|
| phone | Yes | E.164 phone selecting the customer whose cart to return. |
get_customerLookup customer by phoneInspect
Return tags, ℳ-credit balance, M Club tier for the customer with the given E.164 phone. Bearer required.
| Name | Required | Description | Default |
|---|---|---|---|
| phone | Yes | E.164 phone number, e.g. +972501234567. |
get_customer_best_dealsPersonalised best deals for a customerInspect
Top deal projections based on the customer's tags + M Club tier. Bearer + phone required.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max deals to return. | |
| phone | Yes | E.164 phone selecting the customer. |
list_brandsList all brandsInspect
Return every brand with product counts and slugs. Bearer required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_ordersList a customer's ordersInspect
Recent orders with 6-axis status (order / payment / fulfillment / delivery / return / review). Bearer + phone required.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-indexed page number. | |
| limit | No | Page size. | |
| phone | Yes | E.164 phone selecting the customer. |
list_payment_linksList pending payment linksInspect
Pending payment_requests on the customer's unpaid orders. Bearer + phone required.
| Name | Required | Description | Default |
|---|---|---|---|
| phone | Yes | E.164 phone selecting the customer. |
list_productsList / search productsInspect
Browse the catalog with tag, brand, near_hex (ΔE shade match), hue_family, and sort filters. Bearer becomes required when passing phone (rewards projection).
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Natural-language query. Cross-lingual semantic search — `lipstick`, `שפתון`, `lápiz labial` each return Hebrew-tagged lipsticks (the sets may differ across languages but are semantically equivalent). Prefer this over `tag` for any category lookup that isn't already in exact Hebrew. | |
| tag | No | Filter by an EXACT tag string. Tags are Hebrew (e.g. שפתון, ביוטי, עיניים, שפתיים). English category names rarely match — use `q` instead for natural-language queries. | |
| page | No | 1-indexed page number. | |
| sort | No | Sort order. Default: relevance. | |
| brand | No | Filter by brand slug or name. | |
| limit | No | Page size, default 20. | |
| phone | No | E.164 phone for per-customer rewards projection. REQUIRES bearer auth. Omit for anonymous catalog browse. | |
| near_hex | No | Target hex color for ΔE-ranked shade matching. Examples: '#C2185B', 'E8D4B8'. Each returned product carries a `shade_match: {hex, delta_e}` field with the closest variant swatch and its perceptual distance. | |
| hue_family | No | Post-filter on hue family. Must be paired with another filter. |
validate_gift_cardValidate a gift card codeInspect
Check a gift card's remaining balance using its code. Public endpoint — no bearer required (gated on knowledge of the code).
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Gift card code (full string as printed on the card). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!