Skip to main content
Glama
brilliant-directories-mcp

brilliant-directories-mcp

Official

updateDesignSettings

Updates design settings by name in one validated, all-or-nothing call and returns the changes plus an undo for rollback.

Instructions

Change design settings by name in one all-or-nothing call, checked like the Design Settings page; returns the changes and an undo.

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": "updateDesignSettings"
  }
}

Input Schema

NameRequiredDescriptionDefault
undoNoAn earlier result's undo, sent alone.
dry_runNo
settingsNo1 to 100 name: value pairs.
home_rowsNoHomepage sections top to bottom (max 15): getDesignSettings block ids. A plain id keeps the section's spacing and background. Send {block, top_spacing, bottom_spacing, background} only to change them (others kept); background rgb(R, G, B) switches the row colour on, "" off. Unlisted sections leave the homepage; rows below are emptied.
user_namedNotrue only when the user's own words name the value this call sends.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.59.691
    • addedInput schema / properties / user_named
      Added value: +{
      +  "description": "true only when the user's own words name the value this call sends.",
      +  "type": "boolean"
      +}
  2. Addedv6.59.638

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so safety is partly covered. The description adds genuinely useful behavior beyond that: the call is all-or-nothing, it is validated like the Design Settings page, and it returns both the changes and an undo token. It does not disclose permission requirements, rate limits, or what a partially-valid payload does, so it improves on the annotations without fully carrying the burden.

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?

A single dense sentence that front-loads the action and atomicity guarantee, then the validation source, then the return. Nothing is redundant, though the semicolon clause about the undo is compressed to the point of being easy to miss.

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

Completeness3/5

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

For a 5-parameter, nested-object mutation with no output schema, the description covers the atomicity guarantee and the return contents, which is the most important gap filled. However it never explains dry_run or the recovery semantics of the undo parameter, and it says nothing about the homepage row reordering described in the schema, which is the most consequential part of the call.

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

Parameters3/5

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

Schema description coverage is 80%, so the schema already documents settings, home_rows, undo and user_named in detail; the baseline is 3. The description only echoes "by name" for settings and "returns ... an undo" for undo, adding no syntax, ranges, or constraints beyond what the schema states.

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?

States a specific verb and resource ("Change design settings by name") and implies the mutation counterpart to getDesignSettings. It does not explicitly contrast itself with any sibling, and the phrase "by name" is slightly vague about what a "name" is, but an agent can tell this is a write path for design settings.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, no alternatives are named, and the dry_run and undo modes are never explained in the description despite being the main decision points for a caller. The only contextual hint is "checked like the Design Settings page", which describes validation rather than routing.

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