Skip to main content
Glama

Update Lead Form Style Preset

update_lead_form_style_preset

Update an existing custom lead form style preset. LPBE rejects default style presets. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "styleId": "<styleId>",
      "typography": "<typography>",
      "color": "<color>",
      "button": "<button>",
      "borderRadius": "<borderRadius>"
    },
    "name": "update_lead_form_style_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYesColor settings for the form.
buttonYesButton style settings for the form.
styleIdYesLead form style preset ID.
typographyYesFont settings for the form.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
borderRadiusYesCorner radius settings for the form.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • removedInput schema / properties / borderRadius / $ref
      Removed value: -"#/properties/typography"
    • addedInput schema / properties / borderRadius / additionalProperties
      Added value: +{
      +  "$ref": "#/properties/typography/additionalProperties"
      +}
    • addedInput schema / properties / borderRadius / description
      Added value: +"Corner radius settings for the form."
    • addedInput schema / properties / borderRadius / type
      Added value: +"object"
    • removedInput schema / properties / button / $ref
      Removed value: -"#/properties/typography"
    • addedInput schema / properties / button / additionalProperties
      Added value: +{
      +  "$ref": "#/properties/typography/additionalProperties"
      +}
    • addedInput schema / properties / button / description
      Added value: +"Button style settings for the form."
    • addedInput schema / properties / button / type
      Added value: +"object"
    • removedInput schema / properties / color / $ref
      Removed value: -"#/properties/typography"
    • addedInput schema / properties / color / additionalProperties
      Added value: +{
      +  "$ref": "#/properties/typography/additionalProperties"
      +}
    • addedInput schema / properties / color / description
      Added value: +"Color settings for the form."
    • addedInput schema / properties / color / type
      Added value: +"object"
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / styleId / description
      Added value: +"Lead form style preset ID."
    • addedInput schema / properties / typography / description
      Added value: +"Font settings for the form."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world write. The description adds real behavioral context: entitlement gating, grace-period warnings, verified resubscribe links, and an explicit abort condition. It does not, however, disclose whether the six required sections replace or merge with the existing preset, which is the key behavioral unknown for an update.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded correctly, but the remaining text is procedural boilerplate with redundancy — 'check business permissions' and 'Call check_business_tool_access before collecting inputs' say nearly the same thing, and the warning/resubscribe instruction is verbose relative to its value.

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?

Permission gating is covered thoroughly, which matters for a gated mutation. For a six-required-parameter write with nested objects and no output schema, though, the description never explains the semantics of the update itself (replace vs. merge) or what shape the style objects expect.

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%, so communityId and styleId are documented and the baseline is 3. The description adds nothing about the four nested style objects (typography, color, button, borderRadius), whose schemas are notably thin, so it does not compensate for the loose nested definitions.

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 first sentence states a specific verb and resource: 'Update an existing custom lead form style preset.' The word 'custom' plus the note that 'LPBE rejects default style presets' partially distinguishes it from the sibling update_lead_form_style, but no sibling is named explicitly, so an agent must still infer the boundary.

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?

Strong when-not guidance: FREE businesses cannot use this tool regardless of feature rows, check_business_tool_access must be called before collecting inputs, and the agent must stop when access is blocked. What is missing is a positive routing statement — when to pick this over update_lead_form_style or the other lead-form update siblings.

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.

Resources