Skip to main content
Glama

Better Design

by io.github.marvkr
OverviewDiscussionsAdmin

Make a Sales Page

make-sales-page

Makes a hosted sales page for one account, with the same page as a one-page PDF, in a catalog design system, from the account's company, website, offer and call-to-action link. Better Design writes the words left out and draws the visual. It returns the page, PNG and PDF links at once, and they show the page when it is ready. Each call uses 3 credits from the user's Better Design account, and it works only on connections that use a Better Design API key from an account with a verified email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional. What you know about the account: its business, its problem, the conversation so far.
offerYesWhat you offer this account and what it gets.
ctaUrlYesWhere the call to action goes, for example your calendar link.
proof1NoOptional. A proof point, such as a result or a customer quote.
proof2NoOptional. A second proof point.
proof3NoOptional. A third proof point.
companyYesThe account's company name.
problemNoOptional. The problem the account has today. Left out, Better Design writes it.
websiteYesThe account's website, for example https://acme.com.
ctaLabelNoOptional. The button label, for example "Book a call".
headlineNoOptional. The page's headline. Left out, Better Design writes it.
designSystemIdYesA catalog design system id from find-design-system, for example "cashmere". It sets the colours and type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / ctaLabel / description
      Previous value: -"The button label, for example \"Book a call\"."New value: +"Optional. The button label, for example \"Book a call\"."
    • removedInput schema / properties / ctaLabel / minLength
      Removed value: -1
    • changedInput schema / properties / ctaUrl / description
      Previous value: -"Where the button goes, for example your calendar link."New value: +"Where the call to action goes, for example your calendar link."
    • removedInput schema / properties / format
      Removed value: -{
-  "description": "\"page\" makes a hosted sales page. \"pdf\" makes the same page as a one-page PDF to leave behind after a call.",
-  "enum": [
-    "page",
-    "pdf"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / headline / description
      Previous value: -"The page's headline, written for this account."New value: +"Optional. The page's headline. Left out, Better Design writes it."
    • removedInput schema / properties / headline / minLength
      Removed value: -1
    • addedInput schema / properties / notes
      Added value: +{
+  "description": "Optional. What you know about the account: its business, its problem, the conversation so far.",
+  "maxLength": 2000,
+  "type": "string"
+}
    • changedInput schema / properties / problem / description
      Previous value: -"Optional. The problem the account has today."New value: +"Optional. The problem the account has today. Left out, Better Design writes it."
    • changedInput schema / required
      Previous value: -[
-  "format",
-  "designSystemId",
-  "website",
-  "company",
-  "headline",
-  "offer",
-  "ctaLabel",
-  "ctaUrl"
-]New value: +[
+  "designSystemId",
+  "company",
+  "website",
+  "offer",
+  "ctaUrl"
+]
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true, but the description adds substantial behavior the annotations cannot convey: a per-call cost (3 credits), an authentication requirement (Better Design API key with verified email), the generated outputs (page, PNG, PDF links returned at once), and that the links resolve/show once ready. This is exactly the extra context the annotations do not carry.

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?

Three sentences, front-loaded with purpose, then generation behavior, then output/cost/auth. Each sentence carries distinct information and nothing is redundant. Slightly dense in the final sentence, but well structured.

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?

With no output schema, the description usefully names the return values (page, PNG and PDF links) and the async "show the page when it is ready" behavior, plus cost and auth prerequisites. For a 12-parameter, non-idempotent generation tool this is nearly complete; only timing/retry semantics for the pending state are left implicit.

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 the schema already documents all 12 parameters including optionality and lengths. The description references several inputs (company, website, offer, call-to-action link, design system) but adds no syntax, format, or constraint beyond what the schema states. Baseline 3 is appropriate.

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 ("Makes") and resource ("a hosted sales page ... with the same page as a one-page PDF"), which cleanly distinguishes it from siblings like make-social-image and plan-video. The scope (one account, catalog design system, source inputs) is concrete enough that an agent can identify the tool 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 Guidelines3/5

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

The description gives usage preconditions ("works only on connections that use a Better Design API key from an account with a verified email") and scoping ("for one account"), which is useful context. However, it never says when to choose this tool over alternatives such as make-social-image, nor any when-not conditions, so usage is only implied.

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

All Better Design toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources