Skip to main content
Glama

Brand kit from a website

make_brand_kit
Destructive

Generates a brand kit from a website URL, extracting logo files, colors, fonts, first-screen and app images into one folder, plus brand and facts notes for design or copy.

Instructions

Use it when the user wants a site's logo, colors, fonts or brand guidelines, or to design, build or animate anything for a product whose site is known. Reads a website in a headless browser, the way it is drawn, and saves its brand in one folder: the logo files cut from their real background (PNG and SVG), the colors with where each one is used, the fonts, the first screen, a brand card, and the app store icon and screenshots when the site links to its apps. BRAND.md is the file to read first and card.png the picture to show the user; brand.json is for tools and _brand.yml for Quarto and Shiny. With facts, it also saves what the site claims about itself, each claim with its page, in FACTS.md, for copy that needs the site's numbers, customers, quotes or prices; a launch film does not read it. An App Store or Google Play listing works as the address, a social profile is refused, and a deeper page is read from the home page. For font files and their licenses, use make_font_kit instead. The brand playbook (makersmcp_playbook) has the whole job. (easybrandkit 0.4.2, on this machine.)

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": {
      "url": "<url>"
    },
    "name": "make_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe product's website, like https://linear.app, or its App Store or Google Play listing. A deeper page is read from the home page, and a social profile is refused.
factsNoAlso save what the site claims about itself, each claim quoted with its page: numbers, testimonials, customers, prices, integrations and security standards, read from the home page and, where its robots.txt allows, the pricing, customers, security, integrations and about pages it links to. For copy that needs those claims. Takes longer (default false).
storesNoAlso save the icon and screenshots of the App Store and Google Play apps the site links to, and the profile pictures of its X, YouTube, LinkedIn, Threads and Pinterest pages (default true). Set to false to skip them.
out_dirNoFolder to save into, absolute or relative to /app. Default: easybrandkit-<host>, where <host> is the site's host without www or the port. A run replaces what an earlier run of this tool left there once it has ended well, and one that fails or is canceled leaves it as it was: give each version its own out_dir. The folder must be empty or hold an earlier run of this tool: any other folder stops it.
wait_secondsNoHow long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them.
timeout_secondsNoGive up after this many seconds (default 120, or 240 with facts). A slow site, or a kit made from a loading screen, can need 240.

Output Schema

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / facts / description
      Previous value: -"Also read what the site claims about itself from its home, pricing, customers, security, integrations and about pages. Takes longer."New value: +"Also save what the site claims about itself, each claim quoted with its page: numbers, testimonials, customers, prices, integrations and security standards, read from the home page and, where its robots.txt allows, the pricing, customers, security, integrations and about pages it links to. For copy that needs those claims. Takes longer (default false)."
    • changedInput schema / properties / out_dir / description
      Previous value: -"Folder to save into, absolute or relative to /app. Default: easybrandkit-{host}."New value: +"Folder to save into, absolute or relative to /app. Default: easybrandkit-<host>, where <host> is the site's host without www or the port. A run replaces what an earlier run of this tool left there once it has ended well, and one that fails or is canceled leaves it as it was: give each version its own out_dir. The folder must be empty or hold an earlier run of this tool: any other folder stops it."
    • changedInput schema / properties / stores / description
      Previous value: -"Set to false to skip app store listings and social profiles."New value: +"Also save the icon and screenshots of the App Store and Google Play apps the site links to, and the profile pictures of its X, YouTube, LinkedIn, Threads and Pinterest pages (default true). Set to false to skip them."
    • changedInput schema / properties / timeout_seconds / description
      Previous value: -"Give up after this many seconds (default 120, or 240 with facts)."New value: +"Give up after this many seconds (default 120, or 240 with facts). A slow site, or a kit made from a loading screen, can need 240."
    • changedInput schema / properties / url / description
      Previous value: -"The website, like https://linear.app"New value: +"The product's website, like https://linear.app, or its App Store or Google Play listing. A deeper page is read from the home page, and a social profile is refused."
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"How long to wait for the result before returning a job_id to wait on. 45 is safe for clients that stop a tool call after 60 seconds."New value: +"How long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them."
    • addedOutput schema / properties / continued
      Added value: +{
      +  "description": "True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / docs
      Added value: +{
      +  "description": "The notes the text shows, and where each one is.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "description": "What to do next, as the Next line says.",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / timeout_seconds / maximum
      Previous value: -900New value: +600
    • changedInput schema / properties / timeout_seconds / minimum
      Previous value: -10New value: +30
    • addedOutput schema / properties / expires_at
      Added value: +{
      +  "description": "When the download links stop working.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / files / items / properties / url
      Added value: +{
      +  "description": "Where to download the file, when the job ran on a server.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The annotations already flag destructiveHint=true and idempotentHint=false, and the description explains exactly why: out_dir must be empty or hold a previous run of this tool, a successful run replaces what an earlier run left there, and a failed or canceled run leaves it untouched, with advice to give each version its own out_dir. It also discloses runtime behavior beyond the annotations — the headless-browser read, that facts takes longer, and that wait_seconds returns a job_id rather than blocking indefinitely.

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?

Usage guidance and the sibling exclusion are correctly front-loaded, but the middle is a long undifferentiated inventory of output files (BRAND.md, card.png, brand.json, _brand.yml, FACTS.md) that the output schema already covers, and the address rules about app store listings and social profiles are stated twice — once in the body and again in the url parameter. The content is useful but not tight; roughly a third could be cut without losing guidance.

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?

For a six-parameter, open-world, destructive tool, the definition covers everything an agent needs before calling: accepted address types, what the folder contains and which file to surface to the user, runtime and job_id handling, out_dir safety rules, and the escape hatch to make_font_kit. Return values are also backed by an output schema, so the file enumeration is redundant rather than compensatory, but nothing material is missing.

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 parameters are already fully documented, and most of the description's parameter-related content (social profile refused, deeper page read from home page, facts taking longer, store assets) restates the schema rather than extending it. The one genuine addition is the runtime warning that some clients cut a call at 60 or 240 seconds, which contextualizes wait_seconds and timeout_seconds, but that is thin added meaning against a complete 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?

The definition names a concrete verb and resource (read a site in a headless browser, save its brand assets into one folder) and enumerates the artifacts produced: logo PNG/SVG, colors, fonts, first screen, brand card, app icons and screenshots. It also distinguishes itself from the nearest sibling by naming make_font_kit for font files and licenses, so an agent can route between the two without inspecting schemas.

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?

It opens with an explicit trigger ('when the user wants a site's logo, colors, fonts or brand guidelines, or to design, build or animate anything for a product whose site is known') and states an exclusion plus the alternative to use instead (make_font_kit for font files and licenses). It also points to makersmcp_playbook for the full job and notes that a launch film does not read FACTS.md, which is a concrete when-not signal.

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