Skip to main content
Glama

Better Design

by io.github.marvkr
OverviewDiscussionsAdmin

Make a Social Image

make-social-image

Makes a LinkedIn-size social image for one account, in a catalog design system, from the account's company, website, offer and call-to-action link. Better Design writes the headline when it is left out and draws the image. It returns the page and PNG links at once, and they show the image when it is ready. Each call uses 2 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.
companyYesThe account's company name.
websiteYesThe account's website, for example https://acme.com.
headlineNoOptional. The image'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. Changed7 schema fields changed
    • addedInput schema / properties / ctaUrl
      Added value: +{
+  "description": "Where the call to action goes, for example your calendar link.",
+  "format": "uri",
+  "maxLength": 2048,
+  "type": "string"
+}
    • changedInput schema / properties / headline / description
      Previous value: -"The image's headline."New value: +"Optional. The image'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"
+}
    • addedInput schema / properties / offer
      Added value: +{
+  "description": "What you offer this account and what it gets.",
+  "maxLength": 1200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / website
      Added value: +{
+  "description": "The account's website, for example https://acme.com.",
+  "format": "uri",
+  "maxLength": 2048,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "designSystemId",
-  "company",
-  "headline"
-]New value: +[
+  "designSystemId",
+  "company",
+  "website",
+  "offer",
+  "ctaUrl"
+]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing cost (2 credits per call), an authentication prerequisite (API key from a verified-email account), an async return behavior (links return immediately but resolve to the image when ready), and the auto-generated headline fallback. These are exactly the operational facts an agent needs before invoking.

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 dense sentences, front-loaded with the purpose, then behavior, then cost/auth constraints. The return-behavior sentence ('returns the page and PNG links at once, and they show the image when it is ready') is slightly awkward but still informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return-value burden and does so (page and PNG links, async readiness). With 7 params, 5 required, and a mutation with cost, the description covers the essentials an agent needs to call correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description adds cross-tool provenance for designSystemId ('from find-design-system') and clarifies headline is auto-written when omitted. Remaining parameters are only covered by the schema, not the description.

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 artifact ('Makes a LinkedIn-size social image') plus the exact source inputs (company, website, offer, CTA link) and design system. The LinkedIn-size/PNG framing clearly separates it from sibling tools like make-sales-page.

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?

Provides real gating context: it operates on one account, requires a connection using a Better Design API key with a verified email, and costs 2 credits per call. It doesn't explicitly name an alternative tool for other image/page needs, so it stops short of explicit when-not guidance.

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