Document Tools

PDF Brand Guidelines

Generate a brand guidelines PDF with logo, palette, typography, and spacing rules

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/pdf-brand-guidelines-pdf' \
  -F 'file=@/path/to/logoFile.ext'

# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/pdf-brand-guidelines-pdf' \
  -F 'brandName=Northwind Atelier' \
  -F 'tagline=Editorial craft for modern products' \
  -F 'logoFile=/public/logo.png' \
  -F 'primaryColor=#1247A6' \
  -F 'secondaryColor=#1B998B' \
  -F 'accentColor=#F46036' \
  -F 'neutralColor=#EAF0F7' \
  -F 'headingFont=Montserrat' \
  -F 'bodyFont=Source Sans Pro' \
  -F 'baseSpacing=8' \
  -F 'pageSize=A4' \
  -F 'landscape=false' \
  -F 'waitUntil=networkidle0' \
  -F 'waitTime=600'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/pdf-brand-guidelines-pdf

Parameters

Name	Type	Required	Description
brandName	text	Yes	—
tagline	text	No	—
logoFile	fileupload required	No	—
primaryColor	color	No	—
secondaryColor	color	No	—
accentColor	color	No	—
neutralColor	color	No	—
headingFont	text	No	—
bodyFont	text	No	—
baseSpacing	number	No	—
pageSize	select	No	—
landscape	checkbox	No	—
waitUntil	select	No	—
waitTime	number	No	—

File-type parameters must be uploaded first via POST /upload/pdf-brand-guidelines-pdf, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON

{
  "filePath": "/public/processing/randomid.ext",
  "fileName": "output.ext",
  "contentType": "application/octet-stream",
  "size": 1024,
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-pdf-brand-guidelines-pdf": {
      "name": "pdf-brand-guidelines-pdf",
      "description": "Generate a brand guidelines PDF with logo, palette, typography, and spacing rules",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=pdf-brand-guidelines-pdf",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "pdf-brand-guidelines-pdf",
    "arguments": {
  "brandName": "Northwind Atelier",
  "tagline": "Editorial craft for modern products",
  "logoFile": "/public/logo.png",
  "primaryColor": "#1247A6",
  "secondaryColor": "#1B998B",
  "accentColor": "#F46036",
  "neutralColor": "#EAF0F7",
  "headingFont": "Montserrat",
  "bodyFont": "Source Sans Pro",
  "baseSpacing": 8,
  "pageSize": "A4",
  "landscape": false,
  "waitUntil": "networkidle0",
  "waitTime": 600
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]