Brand kit from a website
make_brand_kitGenerates 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
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 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. | |
| facts | No | 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). | |
| stores | No | 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. | |
| out_dir | No | 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. | |
| wait_seconds | No | 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. | |
| timeout_seconds | No | 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. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kit | Yes | ||
| docs | No | The notes the text shows, and where each one is. | |
| next | No | What to do next, as the Next line says. | |
| tool | Yes | ||
| files | No | ||
| folder | No | Where the kit saved its files. | |
| job_id | Yes | ||
| passed | No | For checks: whether the check passed. | |
| status | Yes | ||
| continued | No | True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another. | |
| exit_code | No | ||
| last_line | No | What the kit was doing last. | |
| expires_at | No | When the download links stop working. | |
| next_action | No | ||
| elapsed_seconds | Yes |