Common workflows

These workflows keep discovery separate from changes. Your MCP client displays each tool's exact parameters and result contract. Review Permissions and safe operation before authorizing a write.

Read and inspect PIM data

Use this pattern to investigate products, attributes, catalogs, categories, contexts, assets, labels, relations, or completeness without changing data.

1. State that the task is read-only.
2. Give a stable business identifier, such as a product number, when possible.
3. Ask the assistant to resolve and show internal IDs and contexts instead of guessing them.
4. Ask for the current value and its source record.
5. Stop after the requested summary.

Use read-only tools only. Find product <product-number>, show its internal ID and current context, summarize its main details and attributes, and list its associated asset IDs. Do not create, update, archive, detach, or delete anything.

Browse the relevant catalog sections for products and attributes, catalogs, categories, and contexts, assets, labels and relations, and completeness.

Plan and perform a controlled update

Use two phases so inspection and execution are separate decisions.

Phase 1: inspect and propose

Ask the assistant to:

1. Retrieve the target record and the definitions or related entities needed to validate the change.
2. Report exact target IDs, current values, proposed values, and the number of records affected.
3. Name the tool it proposes to call and summarize the operation's effect.
4. Explain how it will verify the result.
5. Stop without calling a write tool.

Inspect product <product-number> and its Color attribute definition. Propose the smallest valid update to set Color to <new-value>. Show the product ID, attribute-definition ID, context, current value, proposed value, and the exact tool you would call. Do not change anything yet.

Phase 2: confirm, execute, and verify

Confirm only if the proposal matches your intent. Restate the approved target and value, allow that specific call, and require a read-back.

I confirm only this update:

- Product ID: <product-id>
- Context: <context-as-returned>
- Attribute-definition ID: <attribute-definition-id>
- Current value: <current-value>
- New value: <new-value>
- Tool: <exact-tool-name>

Make that one change, then read the product again and compare the returned value with <new-value>. Stop without making a change if any target, value, context, or required tool differs.

For bulk, archive, delete, detach, replacement, publication, or upload-completion actions, apply the additional safeguards in Permissions and safe operation. A prose proposal is not a server-side preview, rollback, or transaction.

Monitor asynchronous work and inspect history

Some operations may return a job identifier. When they do:

1. Retain the job identifier and the original operation summary.
2. Ask the assistant to inspect the job without submitting the mutation again.
3. Continue only until the returned job data indicates a terminal outcome.
4. Treat a failed or ambiguous result as unresolved; do not assume that retrying the original write is safe.
5. Read the target record again after successful completion.

Inspect job ID <job-id> using read-only tools. Report its current state and any available result or error details. Do not resubmit the original operation.

When you need an audit trail for a supported entity, retrieve its history after resolving the exact entity ID. History availability and event detail depend on the entity and the signed-in user's access.

Retrieve available history for entity ID <entity-id>. Summarize the actor, timestamp, and change details that are actually returned, and say which of those fields are absent. Do not modify the entity.

See Asynchronous jobs and History and audit events in the tool catalog.

Search and retrieve Bluestone platform guidance

The product MCP server can search indexed Bluestone guidance, retrieve full content by identifier, and surface recently updated pages. This workflow reads guidance; it does not operate on PIM data.

1. Describe the problem and include relevant Bluestone terminology.
2. Ask for a guidance search before requesting an answer.
3. Ask the assistant to retrieve the most relevant result in full.
4. Require page titles or content identifiers so you can distinguish retrieved guidance from the assistant's inference.
5. For time-sensitive topics, ask it to check recently updated guidance as well.

Search Bluestone platform guidance for modeling variants. Retrieve the most relevant guidance in full, identify the page title or content ID, and summarize the recommendation. Do not read or change organization PIM data.

See Platform guidance in the catalog. For published Bluestone PIM API endpoints and OpenAPI contracts, use the separate docs MCP server.

Work with tasks and users

Task operations can create shared work, change assignees, add products or comments, and mark work complete. Resolve product and user IDs with read-only operations. The MCP server provides tools to read users and task comments, but it does not provide a task-details lookup. Use Bluestone PIM as the trusted read surface for a task's current state and assignee.

Use read-only tools to find the intended user. Verify task <task-id>'s current assignee and state in Bluestone PIM because this connection does not provide a task-details lookup. Do not update or complete the task until I confirm the exact task and user IDs after checking that current state.

See Tasks and users for the task and user tools. Bluestone enforces the signed-in user's permissions when a tool runs. After a confirmed task mutation, use a read tool when available or verify the result in Bluestone PIM. Do not label the task change verified until one of those checks succeeds.