Skip to main content
Glama

Publish a brand stylesheet

publish_portal_stylesheet
Destructive

[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

NameRequiredDescriptionDefault
filesNoPublish the drafts of only these CSS files; the others stay as they were last published.
portalYes`interview` (career and interview portal) or `consumer` (coaching portal). Only the interview portal has brands.
brand_idNoThe sub-brand to publish.
llm_modelNoYour model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
merchant_idNoOptional company. Admins and sub-merchant operators only; other callers always use their token's company.
conversation_idNoThe 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

NameRequiredDescriptionDefault
urlYes
hashYes
warningsYes
size_bytesYes
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / brand_id / description
      Previous value: -"The sub-brand to publish. Leave it out for the main brand, the company's own."New value: +"The sub-brand to publish."
    • changedInput schema / properties / files / description
      Previous value: -"Publish the drafts of only these CSS files; the others stay as they were last published. Leave it out to publish every draft of this brand."New value: +"Publish the drafts of only these CSS files; the others stay as they were last published."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, e.g. \"claude-opus-4-8\"; \"unknown\" if unsure. For analytics.",
      +  "type": "string"
      +}
    • removedInput schema / properties / merchant_id / example
      Removed value: -"28106cba-1c27-4e53-b149-32113e5e8e31"
    • removedInput schema / properties / portal / example
      Removed value: -"interview"
    • removedOutput schema / properties / hash / description
      Removed value: -"First 16 characters of the SHA-256 of the stylesheet."
    • removedOutput schema / properties / hash / example
      Removed value: -"9f86d081884c7d65"
    • removedOutput schema / properties / size_bytes / description
      Removed value: -"Size of the stylesheet."
    • removedOutput schema / properties / size_bytes / example
      Removed value: -18230
    • removedOutput schema / properties / url / description
      Removed value: -"Address of the built stylesheet. It is named after its content and never changes."
    • removedOutput schema / properties / warnings / description
      Removed value: -"Worth telling the person, none of them stopped the publish: over 500 KB, rules outside .jm-site that reach the rest of the portal, removed \"<\" characters."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds materially beyond that: publishing is immediate and affects the live site, it is admin-scoped, partial-file publishing leaves other files at their last published state, and it returns warnings such as rules outside .jm-site.

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 action and its live-site consequence, then defaults, then return warnings. Every sentence carries information; the trailing pointer to get_tool_reference is a useful signpost rather than filler, though it slightly dilutes the core statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, admin-only publish operation with an output schema already covering return shape, the description supplies the missing essentials: admin gating, immediacy and irreversibility of the live change, brand defaulting, and the notable warning category. Nothing an agent needs before invoking it is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: omitting brand_id publishes the main brand, and the files argument's effect on unpublished files is framed in workflow terms. It also routes to get_tool_reference for full argument detail rather than duplicating it.

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?

The first sentence gives a specific verb+resource ("Build one brand's stylesheet ... and put it live") with the source inputs named (style settings and CSS files). It is clearly distinguishable from the sibling draft-writing tools it references, update_portal_configuration and save_component_style.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes the workflow position: it publishes drafts that update_portal_configuration and save_component_style wrote, and notes the brand_id default (main brand when omitted). It stops short of explicit when-not guidance, but the draft-publishing framing makes the selection condition clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.