Skip to main content
Glama
brilliant-directories-mcp

brilliant-directories-mcp

Official

updatePageCss

Idempotent

Add, replace, or remove individual CSS rules by selector in a page's CSS field while leaving all other characters untouched, with undo support to restore previous rules.

Instructions

Add, replace or remove individual CSS rules in a web page's CSS field by selector - every other character of the field is left as it is. An icon is a Bootstrap Icons 1.13.1 icon unless the user names another icon set: write content: bi(NAME) with the name from <i class="bi bi-NAME">, and the tool writes the glyph and its font.

Returns: results (one action per rule: added, replaced, removed, unchanged, not_found) and undo, which is this tool's own input for putting the previous rules back.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "updatePageCss"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesNo1 to 40 rules.
recipeNoInstead of rules: the name of a block's measured rule set, which the tool saves whole on the Home page. hero.search_box is the one recipe.
removeNoOnly with recipe, without values: true takes the recipe and every rule written on the hero search form off the Home page, so the search shows BD's own look again.
seo_idNoThe page. Omit for the site's Home page.
valuesNoOnly with recipe: the look to change, or which of the search fields a visitor must fill. Its block names the keys.
user_namedNotrue only when the user's own words name the value this call sends.
recipe_undoNoOnly as part of the undo a recipe call returned: send that undo whole, as it came.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv6.59.691
    • addedInput schema / properties / recipe_undo
      Added value: +{
      +  "description": "Only as part of the undo a recipe call returned: send that undo whole, as it came.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / remove
      Added value: +{
      +  "description": "Only with recipe, without values: true takes the recipe and every rule written on the hero search form off the Home page, so the search shows BD's own look again.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / rules / items / properties / whole
      Added value: +{
      +  "description": "Only to drop properties a rule already has: true makes css the whole rule. Without it, css that leaves out a property the rule has is refused.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / user_named
      Added value: +{
      +  "description": "true only when the user's own words name the value this call sends.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / values / description
      Previous value: -"Only with recipe: the look to change. Its block names the keys."New value: +"Only with recipe: the look to change, or which of the search fields a visitor must fill. Its block names the keys."
  2. Changed3 schema fields changedv6.59.659
    • addedInput schema / properties / recipe
      Added value: +{
      +  "description": "Instead of rules: the name of a block's measured rule set, which the tool saves whole on the Home page. hero.search_box is the one recipe.",
      +  "type": "string"
      +}
    • addedInput schema / properties / values
      Added value: +{
      +  "description": "Only with recipe: the look to change. Its block names the keys.",
      +  "type": "object"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "rules"
      -]
  3. Addedv6.59.638

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description explains that only targeted rules change, that other characters are preserved, that rule actions are reported, and that an undo value can restore previous rules. That meaningfully clarifies the mutation behavior. It does not discuss permissions, rate limits, or broader side effects, so it is strong but not exhaustive.

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?

The definition is front-loaded with the core behavior and then adds targeted details about icons and return values. Information is dense but generally earns its place. The icon instruction is lengthy, though relevant to correct invocation.

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

Completeness4/5

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

For a relatively complex 7-parameter tool, the description covers the main operation, special icon formatting, return actions, and undo behavior. It omits the recipe/remove path from the prose, but the schema describes those parameters, and annotations cover safety. No output schema exists, and the description supplies the important return-shape information.

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 most parameter meaning is already supplied by the schema. The description adds useful semantics beyond the schema by explaining how to write icon values with Bootstrap Icons syntax and the `content: bi(NAME)` form. It does not explain recipe or values parameters in prose, but those are covered in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: add, replace, or remove individual CSS rules in a web page's CSS field by selector. It also clarifies that it edits only the targeted rules and leaves every other character untouched. It does not explicitly name an alternative sibling such as updateWebPage, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

The description makes the operational scope clear enough to imply usage for surgical CSS rule edits, and it gives icon-specific usage guidance. However, it does not explicitly say when to use this tool instead of updateWebPage or other siblings, nor does it name exclusions.

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

Deploy Server

Other Tools