hdls PIM

hdls PIM is a headless, MCP-native product information management backend. It manages products, attributes, and categories, operated entirely through named tools your AI assistant calls. It stands in for tools like Akeneo, Salsify — same job, no UI to run.

💬 Just ask

"Create a product for Acme, then show me my products."

You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.

How PIM is organized

The headline entity is the product — start there, then attach the rest to it. Records connect by reference: a product_category links to a product and a category. The product_change table is an append-only timeline — every change and note lands there and is never edited or deleted.

Entity	Purpose	Relates to
`product`	An enriched product record carrying structured attribute values plus semantic search.	—
`category`	Hierarchical catalog tree; products are filed into one or more categories.	—
`attribute`	Typed, reusable attribute definition (the PIM field catalog) referenced by product values.	—
`product_category`	Many-to-many membership linking a product to the categories it belongs to.	`product`, `category`
`product_change`	Append-only audit trail of every enrichment/edit applied to a product.	`product`

Tools

Call these at https://hdls.ai/api/mcp/pim. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.

Create

Tool	What it does	Required	Optional
`create_product`	Create a new product.	`sku`, `title`	`family`, `body`, `status`, `completeness`, `values`, `data`

Update & advance

Tool	What it does	Required	Optional
`update_product`	Update an existing product by `id`.	`id`	`sku`, `title`, `family`, `body`, `status`
`set_attribute`	Set the attribute.	`id`	—

Find & read

Tool	What it does	Required	Optional
`search_products`	Search products by free-text and/or column filters (tenant-scoped, paginated).	—	`search`, `filters`, `limit`, `orderBy`
`list_categories`	Search categories by free-text and/or column filters (tenant-scoped, paginated).	—	`search`, `filters`, `limit`, `orderBy`

Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.

Field reference

Every field you can set on each record. Custom fields you add live alongside these in data.

`product`

Field	Type	Required	Notes
`sku`	text	Yes
`family`	text
`title`	text	Yes	Display name.
`body`	text
`status`	text		Lifecycle state.
`completeness`	number
`values`	json
`data`	json		Free-form JSON — custom fields live here.

`category`

Field	Type	Required	Notes
`parent_id`	id		Reference to a related record.
`code`	text	Yes
`name`	text	Yes	Display name.
`description`	text
`position`	number
`data`	json		Free-form JSON — custom fields live here.

`attribute`

Field	Type	Required	Notes
`code`	text	Yes
`label`	text	Yes
`type`	text
`is_required`	true / false
`is_localizable`	true / false
`options`	json
`data`	json		Free-form JSON — custom fields live here.

`product_category`

Field	Type	Required	Notes
`product_id`	id	Yes	Links to a `product`.
`category_id`	id	Yes	Links to a `category`.
`is_primary`	true / false

Tailor it with custom fields

Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.

Roles & safety

Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass tenant_id, and you can only ever see your own data (enforced by Postgres row-level security).
Role-gated. Permissions run reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner.
History is append-only. The product_change timeline is never edited or deleted — it's your audit trail.

Connect

On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "pim" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/pim as a connector in your assistant — see Connect your assistant.

A worked example

The literal call your assistant makes when you ask it to create the headline record:

Tool: create_product
Arguments: {
  "sku": "example",
  "title": "Acme Corp"
}

See All products · Connect your assistant · Automation