Skip to main content
Glama

Update brand settings

update_settings
Destructive

Change the brand's profile, writing rules or Autopilot, or add / remove a brand. operation: add_brand = add a brand within the plan's sites (url, name); remove_brand = PERMANENTLY delete a brand and its data (brand, confirm_name); instructions = set or append writing rules, binding on every article; autopilot = turn Autopilot on or off (on); profile = offer, category, about, language, countries, served area. Without confirm: true NOTHING changes: you get a preview. Show it to the user and call again with confirm: true only after they approve it.

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": {
      "operation": "<operation>"
    },
    "name": "update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoOnly for operation autopilot. true = Autopilot ON, false = OFF.
urlNoOnly for operation add_brand. The brand's site, e.g. "example.com".
modeNoOnly for operation instructions. replace (default) or append.
nameNoOnly for operation add_brand. Brand name (default: the domain).
aboutNoOnly for operation profile. What AI should know about the brand (facts, proof, positioning).
brandNoBrand id, name or domain to remove (required).
offerNoOnly for operation profile. What the brand sells, in one or two sentences.
confirmNoLeave out (or false) to get a preview: nothing changes. Set true ONLY after the user approved that exact preview.
categoryNoOnly for operation profile. The brand's category, e.g. "CRM software".
languageNoOnly for operation profile. Main language, e.g. "French (fr)".
operationYesWhat to do.
target_geoNoOnly for operation profile. Main country tracked, e.g. "France".
target_geosNoOnly for operation profile. Extra tracked countries (plan cap).
confirm_nameNoOnly for operation remove_brand. The brand's exact name, typed by the user, required with confirm: true.
instructionsNoOnly for operation instructions. The instructions text (replace) or the rule to add (append). Empty with replace clears them.
service_areaNoOnly for operation profile. City or area a local business serves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes further by declaring that remove_brand PERMANENTLY deletes a brand and its data, requires an exact typed confirm_name, and that instructions are binding on every article. It also documents the dry-run aesthetic ('nothing changes: you get a preview'), which is behavior no annotation conveys.

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 opening clause is front-loaded and there is essentially no filler, but the operation breakdown is delivered as one long semicolon-chained sentence that is denser to parse than a short list would be. Every clause carries information, so nothing needs cutting, only reformatting.

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 16-parameter, five-operation destructive tool with no output schema, the description covers the prerequisites (confirm gate, confirm_name typing), the destructive consequence, and the per-operation parameter mapping. It omits what the preview response contains and what happens on plan-cap failures for add_brand/target_geos, which keeps it short of fully complete.

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 100% and each parameter already carries an 'Only for operation X' note, so the description largely restates what the schema documents. It does add small amounts of meaning the schema lacks, such as instructions being 'binding on every article' and the plan-scoped limits on add_brand/geos, but this is incremental rather than compensating for gaps.

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 description names a specific mutation scope and then enumerates all five operations (add_brand, remove_brand, instructions, autopilot, profile) with the key parameter for each. An agent can pick the right operation without opening the schema, and the add/remove-brand scope is clearly distinct from the article and reporting siblings.

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 confirm-gating workflow is spelled out explicitly: without confirm:true nothing changes, the preview must be shown to the user, and confirm:true is only called after approval. That is strong when-to-use guidance for the write path, though it never states exclusions or points to a sibling for related tasks (e.g. article editing).

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.