Publish a brand stylesheet
publish_portal_stylesheet[Admin] Build one brand's stylesheet from its style settings and CSS files and put it live at once. Without brand_id it is the main brand. It publishes the drafts update_portal_configuration and save_component_style wrote. Publishing is immediate and changes the live site. Returns warnings, notably rules outside .jm-site.
Every argument in full, with examples: get_tool_reference.
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": {
"portal": "<portal>"
},
"name": "publish_portal_stylesheet"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | No | Publish the drafts of only these CSS files; the others stay as they were last published. | |
| portal | Yes | `interview` (career and interview portal) or `consumer` (coaching portal). Only the interview portal has brands. | |
| brand_id | No | The sub-brand to publish. | |
| llm_model | No | Your model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics. | |
| merchant_id | No | Optional company. Admins and sub-merchant operators only; other callers always use their token's company. | |
| conversation_id | No | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| hash | Yes | ||
| warnings | Yes | ||
| size_bytes | Yes | ||
| _mcp_instructions | No | Server-issued metadata for this conversation. |