Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Set the CRM minisite

crm_set_minisite
DestructiveIdempotent

Saves the client minisite on this account. Does not save unless confirm is true. branding may include display_name, logo_storage_key, and colours. A colour is a short name and a #RGB or #RRGGBB value. pages are in order. Each page has a label, an optional icon, and sections in order. A section type is model, booking, wallet, or text. model points at a list, or at a saved view when view is set. booking does not need a list when this account has one list with scheduling. Name the list when it has more than one. wallet has no list. text is the words to show. menu uses the same shape as crm_set_menu: lists and groups, nested up to 3 levels, and optional icons. A saved view is not a menu item. This does not make a field client-visible. The portal still hides anything that is not client-visible. Use crm_set_client_visibility for that. A list or a view that is not on this account is refused.

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": {
      "confirm": "<confirm>",
      "pages": "<pages>"
    },
    "name": "crm_set_minisite"
  }
}

Input Schema

NameRequiredDescriptionDefault
menuNoMinisite menu, in the same shape as crm_set_menu items.
pagesYesPages, in order.
confirmYesMust be true. A call without confirm true does not save.
brandingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / menu / items / properties / children / description
      Previous value: -"Items under this group. A child is a list or a saved view, not another group."New value: +"Lists or groups under this item. A list's children are lists. A group may contain groups. A saved view is not a menu item."
    • addedInput schema / properties / menu / items / properties / children / items / properties / children
      Added value: +{
+  "description": "Lists or groups under this item. A list's children are lists. A group may contain groups. A saved view is not a menu item.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "icon": {
+        "description": "Ionicon outline name, such as calendarOutline or peopleOutline. Short names such as calendar, people, list, ticket, cpu, bolt, and shirt are accepted.",
+        "enum": [
+          "peopleOutline",
+          "personOutline",
+          "calendarOutline",
+          "timeOutline",
+          "cartOutline",
+          "cubeOutline",
+          "documentTextOutline",
+          "briefcaseOutline",
+          "listOutline",
+          "homeOutline",
+          "cashOutline",
+          "imageOutline",
+          "callOutline",
+          "mailOutline",
+          "pricetagOutline",
+          "constructOutline",
+          "heartOutline",
+          "starOutline",
+          "clipboardOutline",
+          "medkitOutline",
+          "restaurantOutline",
+          "carOutline",
+          "businessOutline",
+          "ribbonOutline",
+          "chatbubblesOutline",
+          "notificationsOutline",
+          "settingsOutline",
+          "gridOutline",
+          "layersOutline",
+          "bookmarkOutline",
+          "flashOutline",
+          "hardwareChipOutline",
+          "receiptOutline",
+          "shirtOutline",
+          "happyOutline",
+          "people",
+          "person",
+          "calendar",
+          "time",
+          "cart",
+          "cube",
+          "documentText",
+          "briefcase",
+          "list",
+          "home",
+          "cash",
+          "image",
+          "call",
+          "mail",
+          "pricetag",
+          "construct",
+          "heart",
+          "star",
+          "clipboard",
+          "medkit",
+          "restaurant",
+          "car",
+          "business",
+          "ribbon",
+          "chatbubbles",
+          "notifications",
+          "settings",
+          "grid",
+          "layers",
+          "bookmark",
+          "flash",
+          "hardwareChip",
+          "receipt",
+          "shirt",
+          "happy",
+          "event",
+          "users",
+          "ticket",
+          "tickets",
+          "cpu",
+          "chip",
+          "bolt",
+          "lightning",
+          "emoji",
+          "smiley"
+        ],
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "model": {
+        "description": "List name. Omit this on a group. A saved view is not a menu item.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "label"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / menu / items / properties / children / items / properties / model / description
      Previous value: -"List name."New value: +"List name. Omit this on a group. A saved view is not a menu item."
    • removedInput schema / properties / menu / items / properties / children / items / properties / view
      Removed value: -{
-  "description": "Saved view name on that list.",
-  "type": "string"
-}
    • changedInput schema / properties / menu / items / properties / children / items / required
      Previous value: -[
-  "label",
-  "model"
-]New value: +[
+  "label"
+]
    • changedInput schema / properties / menu / items / properties / model / description
      Previous value: -"List name. Omit this on a group."New value: +"List name. Omit this on a group. A saved view is not a menu item."
    • removedInput schema / properties / menu / items / properties / view
      Removed value: -{
-  "description": "Saved view name on that list.",
-  "type": "string"
-}
  2. Changed9 schema fields changed
    • changedInput schema / properties / menu / items / properties / children / items / properties / icon / description
      Previous value: -"Optional Ionicons outline name from crm_set_navigation."New value: +"Ionicon outline name, such as calendarOutline or peopleOutline. Short names such as calendar, people, list, ticket, cpu, bolt, and shirt are accepted."
    • addedInput schema / properties / menu / items / properties / children / items / properties / icon / enum
      Added value: +[
+  "peopleOutline",
+  "personOutline",
+  "calendarOutline",
+  "timeOutline",
+  "cartOutline",
+  "cubeOutline",
+  "documentTextOutline",
+  "briefcaseOutline",
+  "listOutline",
+  "homeOutline",
+  "cashOutline",
+  "imageOutline",
+  "callOutline",
+  "mailOutline",
+  "pricetagOutline",
+  "constructOutline",
+  "heartOutline",
+  "starOutline",
+  "clipboardOutline",
+  "medkitOutline",
+  "restaurantOutline",
+  "carOutline",
+  "businessOutline",
+  "ribbonOutline",
+  "chatbubblesOutline",
+  "notificationsOutline",
+  "settingsOutline",
+  "gridOutline",
+  "layersOutline",
+  "bookmarkOutline",
+  "flashOutline",
+  "hardwareChipOutline",
+  "receiptOutline",
+  "shirtOutline",
+  "happyOutline",
+  "people",
+  "person",
+  "calendar",
+  "time",
+  "cart",
+  "cube",
+  "documentText",
+  "briefcase",
+  "list",
+  "home",
+  "cash",
+  "image",
+  "call",
+  "mail",
+  "pricetag",
+  "construct",
+  "heart",
+  "star",
+  "clipboard",
+  "medkit",
+  "restaurant",
+  "car",
+  "business",
+  "ribbon",
+  "chatbubbles",
+  "notifications",
+  "settings",
+  "grid",
+  "layers",
+  "bookmark",
+  "flash",
+  "hardwareChip",
+  "receipt",
+  "shirt",
+  "happy",
+  "event",
+  "users",
+  "ticket",
+  "tickets",
+  "cpu",
+  "chip",
+  "bolt",
+  "lightning",
+  "emoji",
+  "smiley"
+]
    • changedInput schema / properties / menu / items / properties / icon / description
      Previous value: -"Optional Ionicons outline name from crm_set_navigation."New value: +"Ionicon outline name, such as calendarOutline or peopleOutline. Short names such as calendar, people, list, ticket, cpu, bolt, and shirt are accepted."
    • addedInput schema / properties / menu / items / properties / icon / enum
      Added value: +[
+  "peopleOutline",
+  "personOutline",
+  "calendarOutline",
+  "timeOutline",
+  "cartOutline",
+  "cubeOutline",
+  "documentTextOutline",
+  "briefcaseOutline",
+  "listOutline",
+  "homeOutline",
+  "cashOutline",
+  "imageOutline",
+  "callOutline",
+  "mailOutline",
+  "pricetagOutline",
+  "constructOutline",
+  "heartOutline",
+  "starOutline",
+  "clipboardOutline",
+  "medkitOutline",
+  "restaurantOutline",
+  "carOutline",
+  "businessOutline",
+  "ribbonOutline",
+  "chatbubblesOutline",
+  "notificationsOutline",
+  "settingsOutline",
+  "gridOutline",
+  "layersOutline",
+  "bookmarkOutline",
+  "flashOutline",
+  "hardwareChipOutline",
+  "receiptOutline",
+  "shirtOutline",
+  "happyOutline",
+  "people",
+  "person",
+  "calendar",
+  "time",
+  "cart",
+  "cube",
+  "documentText",
+  "briefcase",
+  "list",
+  "home",
+  "cash",
+  "image",
+  "call",
+  "mail",
+  "pricetag",
+  "construct",
+  "heart",
+  "star",
+  "clipboard",
+  "medkit",
+  "restaurant",
+  "car",
+  "business",
+  "ribbon",
+  "chatbubbles",
+  "notifications",
+  "settings",
+  "grid",
+  "layers",
+  "bookmark",
+  "flash",
+  "hardwareChip",
+  "receipt",
+  "shirt",
+  "happy",
+  "event",
+  "users",
+  "ticket",
+  "tickets",
+  "cpu",
+  "chip",
+  "bolt",
+  "lightning",
+  "emoji",
+  "smiley"
+]
    • changedInput schema / properties / pages / items / properties / icon / description
      Previous value: -"Optional Ionicons outline name."New value: +"Ionicon outline name, such as calendarOutline or peopleOutline. Short names such as calendar, people, list, ticket, cpu, bolt, and shirt are accepted."
    • addedInput schema / properties / pages / items / properties / icon / enum
      Added value: +[
+  "peopleOutline",
+  "personOutline",
+  "calendarOutline",
+  "timeOutline",
+  "cartOutline",
+  "cubeOutline",
+  "documentTextOutline",
+  "briefcaseOutline",
+  "listOutline",
+  "homeOutline",
+  "cashOutline",
+  "imageOutline",
+  "callOutline",
+  "mailOutline",
+  "pricetagOutline",
+  "constructOutline",
+  "heartOutline",
+  "starOutline",
+  "clipboardOutline",
+  "medkitOutline",
+  "restaurantOutline",
+  "carOutline",
+  "businessOutline",
+  "ribbonOutline",
+  "chatbubblesOutline",
+  "notificationsOutline",
+  "settingsOutline",
+  "gridOutline",
+  "layersOutline",
+  "bookmarkOutline",
+  "flashOutline",
+  "hardwareChipOutline",
+  "receiptOutline",
+  "shirtOutline",
+  "happyOutline",
+  "people",
+  "person",
+  "calendar",
+  "time",
+  "cart",
+  "cube",
+  "documentText",
+  "briefcase",
+  "list",
+  "home",
+  "cash",
+  "image",
+  "call",
+  "mail",
+  "pricetag",
+  "construct",
+  "heart",
+  "star",
+  "clipboard",
+  "medkit",
+  "restaurant",
+  "car",
+  "business",
+  "ribbon",
+  "chatbubbles",
+  "notifications",
+  "settings",
+  "grid",
+  "layers",
+  "bookmark",
+  "flash",
+  "hardwareChip",
+  "receipt",
+  "shirt",
+  "happy",
+  "event",
+  "users",
+  "ticket",
+  "tickets",
+  "cpu",
+  "chip",
+  "bolt",
+  "lightning",
+  "emoji",
+  "smiley"
+]
    • addedInput schema / properties / pages / items / properties / sections / items / properties / icon / description
      Added value: +"Ionicon outline name, such as calendarOutline or peopleOutline. Short names such as calendar, people, list, ticket, cpu, bolt, and shirt are accepted."
    • addedInput schema / properties / pages / items / properties / sections / items / properties / icon / enum
      Added value: +[
+  "peopleOutline",
+  "personOutline",
+  "calendarOutline",
+  "timeOutline",
+  "cartOutline",
+  "cubeOutline",
+  "documentTextOutline",
+  "briefcaseOutline",
+  "listOutline",
+  "homeOutline",
+  "cashOutline",
+  "imageOutline",
+  "callOutline",
+  "mailOutline",
+  "pricetagOutline",
+  "constructOutline",
+  "heartOutline",
+  "starOutline",
+  "clipboardOutline",
+  "medkitOutline",
+  "restaurantOutline",
+  "carOutline",
+  "businessOutline",
+  "ribbonOutline",
+  "chatbubblesOutline",
+  "notificationsOutline",
+  "settingsOutline",
+  "gridOutline",
+  "layersOutline",
+  "bookmarkOutline",
+  "flashOutline",
+  "hardwareChipOutline",
+  "receiptOutline",
+  "shirtOutline",
+  "happyOutline",
+  "people",
+  "person",
+  "calendar",
+  "time",
+  "cart",
+  "cube",
+  "documentText",
+  "briefcase",
+  "list",
+  "home",
+  "cash",
+  "image",
+  "call",
+  "mail",
+  "pricetag",
+  "construct",
+  "heart",
+  "star",
+  "clipboard",
+  "medkit",
+  "restaurant",
+  "car",
+  "business",
+  "ribbon",
+  "chatbubbles",
+  "notifications",
+  "settings",
+  "grid",
+  "layers",
+  "bookmark",
+  "flash",
+  "hardwareChip",
+  "receipt",
+  "shirt",
+  "happy",
+  "event",
+  "users",
+  "ticket",
+  "tickets",
+  "cpu",
+  "chip",
+  "bolt",
+  "lightning",
+  "emoji",
+  "smiley"
+]
    • changedInput schema / properties / pages / items / properties / sections / items / properties / model / description
      Previous value: -"List name for a model, saved view, or booking block."New value: +"List name for a model or saved view. Omit it on a booking block to use this account's booking list."
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses that nothing saves unless confirm is true and that off-account lists/views are refused, which is meaningful operational context. It does not state whether an existing minisite is replaced or what happens to pages omitted from the call, which is the main destructive behavior an agent needs to know.

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 the confirm gate, then organized by parameter (branding, pages, sections, menu) in a logical walk-through. Some sentences restate schema structure (page label/icon, sections in order) that could be trimmed, but most sentences carry non-obvious rules.

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 deeply nested four-parameter destructive write with no output schema, the description covers nesting limits, per-section-type rules, validation failures, and the visibility caveat. The remaining gap is failure/replacement semantics: whether a partial or removed page is deleted and what a refusal returns.

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

Parameters5/5

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

The description adds substantial meaning beyond the 75%-covered schema: colour values are #RGB/#RRGGBB, section types model/booking/wallet/text with per-type list rules (booking omits list when the account has one scheduling list, name it when there are several, wallet takes none), view selection for model sections, and menu nesting capped at 3 levels. It also clarifies that a saved view is not a menu item, resolving a real ambiguity in the nested menu schema.

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?

"Saves the client minisite on this account" names a specific verb and resource, and the description distinguishes the tool from crm_set_menu (shape reference), crm_get_minisite (implied read), and crm_set_client_visibility (which it explicitly redirects to). An agent can identify the resource and scope without opening the schema.

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 gives clear when-to-use context and an explicit alternative for the visibility concern ("Use crm_set_client_visibility for that"), plus the confirm gate. It does not explain how this relates to crm_set_navigation, crm_set_dashboard, or crm_set_branding, which overlap with the minisite's branding/menu fields, so the routing space is not fully closed.

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

All Widely toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources