Skip to main content
Glama
Sign In

Youform

by io.github.mkmaker
OverviewDiscussionsAdmin

Update design

update-design-tool
Destructive

Update a form's visual design. Send only the design keys you want to change. Omitted keys retain their current values, including logos, custom fonts, and advanced settings. Editable keys: font (string), align (left|center), corner (straight|rounded-sm|circular), font-size (small|medium|large), logo-size (small|medium|large), logo-alignment (left|right|center), text-color, rating-color, background-color, answer-text-color, button-text-color, button-background-color (all #RRGGBB hex), background-image-url (url). Advanced keys (resources/design/advanced-schema.json) are accepted too: form-width-px, card + card-* (background-color/opacity, radius-px, backdrop-blur-px, border-enabled/width/style/color/opacity, shadow none|sm|md|lg|hard|custom with shadow-x/y/blur/spread/color/opacity), title-/label- typography (font, size-px, weight, tracking, align), body-size-px, description-size-px, input-style underline|box plus input-/option-/button-* surface keys (background-color/opacity, text-color, radius-px, border-, shadow-), button-align, submit-icon none|check|arrow, padding and gap keys. Design changes apply to the live form immediately — no publish needed. If get-form-tool returns design: null the form uses defaults — pass a new object with just the keys you want to set (at least one key is required).

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": {
      "form_slug": "<form_slug>",
      "design": "<design>"
    },
    "name": "update-design-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
designYesDesign keys to change. Omitted keys are preserved.
form_slugYesThe form's slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds valuable context beyond annotations: changes apply to the live form immediately with no publish step, which is the key operational consequence for a destructiveHint=true tool. Omissions are clarified as preserve-by-default, reducing risk of accidental overwrites. It does not discuss permissions or reversibility of the change, keeping it below a 5.

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

Conciseness2/5

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

The enumeration of dozens of advanced keys is dense and hard to parse, with nested card-*/shadow-* notation crammed into one run-on sentence. Front-loading of the core behavior is good, but the bulk of the text buries the actionable facts and could have been deferred to a schema reference.

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?

Covers mutation semantics, defaults, and key enumeration, which is substantial for a 2-parameter tool. However, with a free-form design object and no output schema, the description is the entire contract yet leaves unclear what happens on invalid keys or whether the response returns the updated design.

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 coverage is 100%, so the baseline is 3. The description adds real value by enumerating allowed keys and value formats (hex colors, enum-ish values for align/corner/font-size), which the schema's generic object type does not express. That borderline lifts it, but the keys are not validated by the schema, so the description is now the only contract.

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?

States a specific verb and resource ('Update a form's visual design') and distinguishes the tool from block-level siblings like update-block-tool by scoping it to design. The enumeration of editable keys makes the boundary unmistakable.

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

Usage Guidelines5/5

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

Explicitly says to send only keys to change, that omitted keys are preserved, that at least one key is required, and points to get-form-tool to check for design: null. It effectively tells the agent the alternative path (create/initialize a design object when null) for the edge case.

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

All Youform 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