# Blaze MCP server Blaze makes and schedules social media content. Its MCP server lets an AI assistant do the same from a chat: plan posts, make on-brand images, carousels and short videos, write blog posts and newsletters, and schedule them to the user's connected channels. - Server URL: `https://app.blaze.ai/mcp` (Streamable HTTP) - Authentication: OAuth 2.1 with dynamic client registration. The user signs in with their Blaze account. New accounts start with a free trial at https://app.blaze.ai/signup. - Works with Claude, ChatGPT, Codex, Cursor and other MCP clients. - Official MCP Registry name: `ai.blaze.app/blaze` - Website: https://www.blaze.ai/mcp ## What it can do - Make posts in the user's brand: single images, carousels, multi-image posts and short vertical videos for Reels, TikTok and YouTube Shorts. - Write blog posts and email newsletters as drafts. - Plan campaigns and a week of posts. - Schedule posts the user already has, with their own captions and media. - Show what's on the calendar, and move, edit, publish or delete posts. - Report followers and impressions for each connected account. - Find reviews that need a reply, draft replies, and post them. ## Channels Instagram, Facebook, LinkedIn, X, Google Business Profile, TikTok and YouTube. Blog posts and newsletters publish through the user's connected blog or email integration. ## Safety New content is saved as a draft. Nothing is published until a post is scheduled or published now, or a review reply is sent. The assistant should confirm the content, channels and times with the user first. Posts only go to accounts the user has connected in Blaze, and the assistant sees only the workspaces the user can see. ## Connect 1. Add `https://app.blaze.ai/mcp` to the assistant's connector or MCP settings. 2. Sign in to Blaze and approve access. 3. Ask, for example: "Plan next week's posts and draft them in Blaze." Client guides: - Claude: https://app.blaze.ai/mcp/docs/claude.md - ChatGPT: https://app.blaze.ai/mcp/docs/chatgpt.md - Codex: https://app.blaze.ai/mcp/docs/codex.md Every tool, with its inputs and whether it changes anything: https://app.blaze.ai/mcp/docs/tools.md ## Example requests - "Make a 6-slide Instagram carousel on our fall menu, in our brand colors." - "Turn this blog post into a LinkedIn post and three X posts, and schedule them for next week." - "Plan a week of posts for our dental practice, with one carousel and one short video." - "What's scheduled for this week? Move Thursday's post to Friday." ## Help - Help Center: https://help.blaze.ai/en/ - Privacy Policy: https://www.blaze.ai/privacy-policy - Terms: https://www.blaze.ai/terms --- # Blaze for Claude Connect Blaze to Claude to make carousels, videos and posts in your brand, then schedule them to Instagram, TikTok, YouTube, LinkedIn and more, from the chat. ## Connect 1. In Claude, open Settings → Connectors and choose Add custom connector. 2. Paste `https://app.blaze.ai/mcp` as the URL. 3. Sign in to Blaze and approve access to your workspaces. The connector works in Claude on the web, the desktop app and Claude Code. In Claude Code you can also run: ``` claude mcp add --transport http blaze https://app.blaze.ai/mcp ``` Claude shows the slides of a design in an interactive preview in the chat. ## Try asking - "Make a 6-slide Instagram carousel on our fall menu, in our brand colors." - "Schedule a post for Friday at 6pm announcing our holiday hours." - "What did we post last week, and how did it do?" ## Good to know - Claude confirms the posts, channels and times with you before scheduling anything. - New content is saved as a draft in Blaze. - If you're in more than one workspace, tell Claude which one to use. More: https://app.blaze.ai/mcp/docs/overview.md · Tools: https://app.blaze.ai/mcp/docs/tools.md --- # Blaze for ChatGPT Use the Blaze app in ChatGPT to make on-brand carousels, videos and posts, preview them in the chat, and schedule them to every channel. ## Connect 1. In ChatGPT, find Blaze in the apps directory and choose Connect. 2. Sign in to Blaze and approve access to your workspaces. 3. Ask ChatGPT to use Blaze, for example: "Use Blaze to make a carousel on our fall menu." Workspace admins can also add the server directly in developer mode: Settings → Apps, then add `https://app.blaze.ai/mcp` with OAuth. ChatGPT shows every slide of a design, and finished posts and images, in a preview in the chat. ## Try asking - "Make a 6-slide Instagram carousel on our fall menu, in our brand colors." - "Turn this blog post into a LinkedIn post and three X posts, and schedule them for next week." - "What's scheduled for this week? Move Thursday's post to Friday." ## Good to know - ChatGPT confirms the posts, channels and times with you before scheduling anything. - New content is saved as a draft in Blaze. - If you're in more than one workspace, tell ChatGPT which one to use. More: https://app.blaze.ai/mcp/docs/overview.md · Tools: https://app.blaze.ai/mcp/docs/tools.md --- # Blaze for Codex The Blaze plugin for Codex plans a week of posts, designs on-brand carousels and schedules them across your social channels. You can install the plugin, or connect the MCP server on its own. ## Connect ``` codex mcp add blaze --url https://app.blaze.ai/mcp codex mcp login blaze ``` The login opens a browser to sign in to Blaze. The Codex CLI and the IDE extension share one configuration, so it works in both. The plugin adds skills on top of the server's tools: plan a week, make a brand carousel, schedule posts, a daily digest, and posts on fast-moving topics. ## Try asking - "Plan next week's posts and draft them in Blaze." - "Make a carousel from docs/launch.md and schedule it for Tuesday morning." - "Upload the images in ./assets and schedule them as an Instagram post." ## Good to know - Codex confirms the posts, channels and times with you before scheduling anything. - New content is saved as a draft in Blaze. More: https://app.blaze.ai/mcp/docs/overview.md · Tools: https://app.blaze.ai/mcp/docs/tools.md --- # Blaze MCP tools The Blaze MCP server at https://app.blaze.ai/mcp has 39 tools. Every tool except list_workspaces and search_fonts takes a workspace_key; call list_workspaces first to get it. Read tools only look things up. Before a tool that publishes or deletes, confirm the content, channels and times with the user. ## list_workspaces List workspaces · Read-only List the Blaze workspaces the signed-in user belongs to. Each entry has the workspace name, the user's role, and the workspace_key that every other workspace-scoped tool requires. Takes no inputs. Read-only. ## get_workspace Get workspace · Read-only Get one workspace's name, key, and id, plus the signed-in user's name, email, and role in it. Input: workspace_key. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. ## get_brand_kit Get brand kit · Read-only Get a workspace's brand kit: brand name and profile; brand voice (purpose, audience, tone, emotions, character, syntax, language); color palettes; logos with asset URLs; and fonts with family, weights, type scale, and specimen links. Use the colors and fonts as inputs to compose_design and the design edit tools. Inputs: workspace_key; optional brand_kit_id. Without brand_kit_id it returns the workspace's most recent brand kit. Returns a notice if the workspace has no brand kit. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `brand_kit_id` (integer, optional): Optional id of a specific brand kit. Defaults to the primary (most recent) kit. ## list_scheduled_posts List scheduled posts · Read-only List a workspace's posts on the content calendar. Each entry has the post id, status, platform, scheduled time, and a short content preview. Optional filters: status (scheduled, processing, published, failed, draft, retrying, or all; default scheduled), type (blog, image, video, or all; default all), from and to (ISO 8601 datetimes), and limit (1-100, default 20). For example, status "published" with type "blog" lists published blog posts. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `status` (string, optional): Filter by post status. Defaults to 'scheduled'. One of: scheduled, processing, published, failed, draft, retrying, all. - `type` (string, optional): Filter by content type: 'blog' (articles), 'image' (designs), 'video'. Defaults to 'all'. One of: blog, image, video, all. - `from` (string, optional): ISO 8601 datetime — only return posts at or after this time. - `to` (string, optional): ISO 8601 datetime — only return posts at or before this time. - `limit` (integer, optional): Max posts to return (1–100). Defaults to 20. ## get_scheduled_post Get scheduled post · Read-only Get one post by its numeric id: content, media, each platform target with its own status, error details, and posting history. For a blog post it also returns a JSON export (rendered HTML body, slug, excerpt, author, tags, cover image) that can be used to display the published post on another site. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `id` (integer, required): The numeric ID of the scheduled post. ## edit_scheduled_post Edit scheduled post · Can overwrite or delete data; reaches outside Blaze Change an existing draft or scheduled post: its publish time (post_at), its caption, per-platform captions, or its status (draft or scheduled). Fields you omit are left as they are. Call get_scheduled_post first to see the post's targets and captions. For a post with one platform, pass caption. For a post sent to several platforms, pass captions with one entry per platform to change; platforms you leave out keep their caption. If a post has two targets on the same platform, identify each by target_id (listed by get_scheduled_post) instead of provider. Setting status to "scheduled" queues the post to publish at post_at to the connected social accounts. Published or in-progress posts cannot be edited and are rejected. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `id` (integer, required): The numeric ID of the scheduled post to edit. - `post_at` (string, optional): New ISO 8601 publish datetime. - `caption` (string, optional): New caption for the post's primary content. For a single-target post this is the post's caption; for a multi-target post it's the fallback used by any platform without its own entry in captions. - `captions` (array of object, optional): Per-platform caption overrides, for posts with more than one target. - `provider` (string, optional): Platform to set the caption for, e.g. "instagram". Not needed if the post has only one target. - `target_id` (integer, optional): Numeric target ID. Only needed to disambiguate when the post has more than one target for the same provider. - `caption` (string, required): This platform's caption. - `status` (string, optional): Move the post between draft and scheduled. One of: scheduled, draft. ## publish_post_now Publish post now · Writes data without deleting any; reaches outside Blaze Publish a draft or scheduled post immediately to the connected social accounts it targets, instead of waiting for its scheduled time. This posts publicly and cannot be undone from Blaze. Confirm the post and its channels with the user before calling. Only draft or scheduled posts with at least one connected, active account can be published. Posts that are already published, publishing, or retrying are rejected so nothing is posted twice. Publishing runs in the background: call get_scheduled_post afterwards to see the result and the live post links. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `id` (integer, required): The numeric ID of the scheduled post to publish. ## delete_scheduled_post Delete scheduled post · Can overwrite or delete data Permanently delete a draft or scheduled post from Blaze, including its per-platform targets. It will not be published. This cannot be undone. Published or in-progress posts are rejected: deleting them in Blaze would not remove them from the social platforms, so they must be deleted on each platform directly. To keep a post but stop it from publishing, use edit_scheduled_post with status "draft" instead. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `id` (integer, required): The numeric ID of the scheduled post to delete. ## generate_post Generate post · Writes data without deleting any Generate one social media post (a single image, a carousel, or a short video) from the workspace's brand plan, and save it as a design with a draft post. Nothing is published. Inputs: workspace_key; optional topic, channel (default instagram_post), content_type (image, carousel, or video; default image), slide_count (carousels only: 2 to 10 slides, default 4; passing it implies a carousel), brand_plan_schedule_id (a campaign id from create_campaign or list_campaigns; omit for a standalone post), and post_at (ISO 8601; default one day from now). Carousels: set the number of slides with slide_count, not in the topic. The carousel has exactly that many slides, or generation fails with the reason. Story channels and campaigns under strict brand control can't make carousels. Video: the instagram_reel, tiktok_post, and youtube_short channels always produce a video, whatever content_type is given. A video is a vertical (9:16) clip of about 8 to 12 seconds. It is either an animated clip (one generated image turned into a single clip of about 8 seconds, with no audio) or a scripted video (three short shots joined together, about 12 seconds, which may include a voiceover and captions when the workspace has them turned on). Which of the two is made is set by the campaign's content strategy; it cannot be chosen here. Generation runs in the background, and videos take longer than images. The tool returns a content id at once; pass it to get_generated_post to get the result, which for a video includes the MP4 link. Requires an active brand plan. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `topic` (string, optional): Optional. What the post should be about (the brief / subject). If omitted, a topic is drawn from the schedule. - `channel` (string, optional): Target channel. Defaults to 'instagram_post'. One of: instagram_post, linkedin_post, facebook_post, google_my_business_post, twitter_post, instagram_story, instagram_reel, tiktok_post, youtube_short, facebook_story. - `content_type` (string, optional): Format to generate. Defaults to 'image'. 'video' produces a short vertical video. Ignored for instagram_reel, tiktok_post, and youtube_short, which always produce video. One of: image, carousel, video. - `slide_count` (integer, optional): Carousels only: how many slides (2-10, default 4). Implies content_type carousel. - `brand_plan_schedule_id` (integer, optional): Optional campaign (schedule) id to attach this post to. Omit for a standalone post. - `post_at` (string, optional): Optional ISO 8601 datetime to schedule the draft for. ## get_generated_post Get generated post · Read-only Get the status of a post started with generate_post, by content id. While it is running, returns the status. When it has finished, returns the design id, a preview image, the draft post's id and time, and the caption. For a video it also returns the link to the MP4 file and its length in seconds when known; the preview image is a still frame. If it failed, returns the reason. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `content_id` (integer, required): The content id returned by generate_post. ## create_doc Create blog post or email · Writes data without deleting any; reaches outside Blaze Create a blog post or email newsletter from Markdown that you write. The tool converts the Markdown (headings, lists, links, emphasis) into a Blaze document, saves it in the workspace, and creates a matching draft post. Nothing is published. Inputs: workspace_key, title, markdown; optional type ("blog" or "email"; default "blog"), project_id (default: the user's default project), and post_at (the draft's intended publish time, ISO 8601). Returns the document id, an editor URL, and the draft post's id. To schedule the draft or change its date or caption, call edit_scheduled_post with that id. Publishing needs a connected blog or email integration in the workspace. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `title` (string, required): The document title. - `markdown` (string, required): The document body as Markdown. Converted to the editor rich-text document. - `type` (string, optional): Document type: 'blog' post or 'email'/newsletter. Defaults to 'blog'. One of: blog, email. - `project_id` (integer, optional): Optional project (in this workspace) to file the doc in. Defaults to your default project. - `post_at` (string, optional): Optional ISO 8601 datetime for the draft scheduled post's intended publish time. ## create_campaign Create campaign · Writes data without deleting any Create a campaign: a named, dated content schedule in the workspace. Inputs: name, start_date (ISO 8601 date), length_weeks; optional brief, topics, call_to_action, target_link. Without topics, Blaze generates the campaign's theme, audience, call to action, and topics from the brief in the background; the tool returns the campaign id right away, and list_campaigns shows the topic count once generation finishes. With topics, those are used as given and nothing is generated. After that, Blaze generates content for the campaign's posting schedule, as it does for campaigns created in the Blaze app. Pass the returned id to generate_post as brand_plan_schedule_id to add a post to this campaign. Requires the workspace to have an active brand plan and an admin member. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `name` (string, required): Display name for the campaign. - `start_date` (string, required): ISO 8601 date the campaign starts. - `length_weeks` (integer, required): Number of weeks the campaign spans. - `brief` (string, optional): What the campaign is about. Seeds theme/topic generation. Omit to generate from the brand context. - `topics` (array of string, optional): Optional explicit topics. If given, these are used and topic generation is skipped; otherwise topics are generated for you. - `call_to_action` (string, optional): Optional call to action text. - `target_link` (string, optional): Optional URL the campaign drives to. ## list_campaigns List campaigns · Read-only List a workspace's campaigns, newest first. Each entry has the campaign id, name, start date, and number of generated topics (use the count to check progress after create_campaign). Inputs: workspace_key; optional limit (1-100, default 20). Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `limit` (integer, optional): Max campaigns to return (1-100). Defaults to 20. ## get_media_upload_urls Get media upload URLs · Writes data without deleting any Get upload URLs for media files that are on the user's computer, so they can be used with schedule_posts. Input: workspace_key and filenames (each with its real extension). For each filename it returns an upload_url and a hosted_url. Upload each file with an HTTP PUT of its raw bytes to its upload_url, for example `curl -X PUT --upload-file ""`. Do not add x-amz-acl or any other x-amz-* header; the URL is already signed and S3 rejects extra signed headers. Then pass each hosted_url to schedule_posts as a media url, in carousel order. The extension sets the media type. Supported images: png, jpeg, webp, svg. Supported videos: mp4, mpeg, webm, quicktime (.mov). Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `filenames` (array of string, required): Local file names to upload, each with its real extension. ## schedule_posts Schedule posts · Writes data without deleting any; reaches outside Blaze Schedule one or more finished social posts that the user already has: their own media, captions, and publish times. Each post needs post_at (ISO 8601), channels, and media. Each channel names a provider (instagram, facebook, linkedin, x, google_business_profile, tiktok, youtube) and an optional caption; a channel without a caption uses the first channel's caption. Several channels make one cross-post that shares the same media and publish time. Media is either images (one, or several for a carousel in the order given) or exactly one video, never both. TikTok and YouTube accept video only. Media type is read from the URL extension unless you pass type. Each url must be publicly reachable; for local files, call get_media_upload_urls first. A post with a connected social account is scheduled and publishes automatically at post_at; any of its channels without a connected account will not publish and are listed in the response. A channel whose account has lost access is flagged with a warning: it will fail to publish until the account is reconnected in Blaze (list_connected_accounts shows each account's status). A post with no connected account, or in a workspace that requires approval, is saved as a draft instead. Invalid posts (missing media, mixed images and video, too many images for a channel, bad date, no channels) are skipped and listed in the response; the others are still scheduled. Retries: give each post an idempotency_key (any unique string) to make retries safe. If the same workspace sends the same key again within 24 hours, the post created the first time is returned and nothing new is created. Without a key, a post identical to one this tool created in the last 10 minutes (same post_at, channels, captions, and media URLs) is also returned instead of being created again; to schedule a true duplicate inside that window, pass a new idempotency_key. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `posts` (array of object, required): The posts to schedule. Each is scheduled independently. - `post_at` (string, required): ISO 8601 datetime to publish at. - `idempotency_key` (string, optional): Optional unique string for this post. Resending the same key within 24 hours returns the post already created instead of a new one. - `channels` (array of object, required): Channels to publish this post to. Multiple channels cross-post the same post to each. The first channel is primary (drives the render). - `provider` (string, required): Social provider for this channel. One of: instagram, facebook, linkedin, x, google_business_profile, tiktok, youtube. - `caption` (string, optional): This channel's caption / copy. Optional; defaults to the first channel's caption. - `channel` (string, optional): Optional channel override (e.g. instagram_reel). Only the first channel affects the render; defaults from provider + media. - `media` (array of object, required): Media URLs in carousel order. One image, several images, or one video. - `url` (string, required): Publicly reachable URL of the image or video. - `type` (string, optional): Optional. Defaults to inference from the URL extension. One of: image, video. ## list_connected_accounts List connected accounts · Read-only List the accounts connected to a workspace: social accounts that schedule_posts can publish to, and blog, email, ads, and other integrations. Use it before scheduling to check that each channel will publish. Each account shows its provider (social providers use the same names schedule_posts accepts), display name, handle when known, account type, status, and when Blaze last checked the connection. Status is "active", "disconnected" (Blaze lost access), or "token expired" (the access token expired and cannot be renewed). Posts to an account that is not active will not publish until it is reconnected in Blaze. Pass provider to list only one provider. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `provider` (string, optional): Optional. Only list accounts for this provider, e.g. "instagram" or "linkedin". ## generate_image Generate image · Writes data without deleting any; reaches outside Blaze Generate an image from a text prompt. Inputs: workspace_key and prompt (subject, style, composition); optional model (nano_banana, nano_banana_2, gpt_image, or seedream; default is the workspace's model), aspect_ratio (for example "1:1", "9:16", "16:9"; default square), apply_visual_style (adds the workspace's brand visual style to the prompt), and reference_image_urls (up to 6 public image URLs, for example from search_media or an earlier result, to keep a subject, product, or person). Generation runs in the background and usually takes 1-5 minutes. The tool returns a request id at once; call get_generated_image with it every 15-30 seconds until it is done. The image is not added to the media library. Its URL can be used in compose_design, set_design_background, or replace_design_image. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `prompt` (string, required): What the image should depict — subject, style, composition. Required. - `model` (string, optional): Optional image model. Omit to use the workspace default. One of: nano_banana, nano_banana_2, gpt_image, seedream. - `apply_visual_style` (boolean, optional): Optional. Layer the workspace's brand visual style onto the prompt. Defaults to false. - `aspect_ratio` (string, optional): Optional aspect ratio, e.g. "1:1", "9:16", "16:9". Defaults to square. - `reference_image_urls` (array of string, optional): Optional public image URLs for image-to-image. Up to 6. ## get_generated_image Get generated image · Read-only Get the status of an image started with generate_image, by request id. While it is running, returns the status; generation usually takes 1-5 minutes, so wait 15-30 seconds between calls. When it has finished, returns the image URL and an inline preview. If it failed, returns the reason. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `id` (integer, required): The request id returned by generate_image. ## search_media Search media library · Read-only Browse or search the photos and videos uploaded to a workspace's media library (these are not part of get_brand_kit). Returned URLs can be used in compose_design, set_design_background, replace_design_image, or as generate_image references. Without query, lists the most recently used uploads, paged with page and limit (default 20, max 50); type selects "image" (default) or "video". With query, runs a semantic search over images only, and only over images Blaze has already indexed, so browsing is the complete list. Each result has a title, hosted URL, MIME type, dimensions, and media key. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `query` (string, optional): Optional. Semantic search over indexed images. Omit to browse recent uploads. - `type` (string, optional): Browse "image" (default) or "video". Ignored when query is set (search is image-only). One of: image, video. - `page` (integer, optional): Optional 1-based page for browse mode. Defaults to 1. - `limit` (integer, optional): Optional page size. Defaults to 20, capped at 50. ## search_fonts Search fonts · Read-only Search the fonts Blaze can render (Google Fonts plus Blaze's licensed catalog) by family name, for example "mono", "grotesk", "slab", or "playfair". Each result has the family name, catalog, category (sans-serif, serif, monospace, display, handwriting), and available weights. Pass a family name unchanged as the font field in compose_design. The workspace's brand fonts come from get_brand_kit. Does not need a workspace_key. Read-only. Parameters: - `query` (string, required): Substring matched against font family names, e.g. "mono", "playfair". Required. - `source` (string, optional): Which catalog to search. Defaults to "both". One of: both, google, blaze. - `category` (string, optional): Optional filter: sans-serif, serif, monospace, display, handwriting. - `limit` (integer, optional): Max results. Defaults to 20, capped at 50. ## compose_design Compose design · Writes data without deleting any; reaches outside Blaze Create a new social media design (a single image or a multi-slide carousel) from a layout you describe in the JSON format below, and save it to the workspace, where it can be opened in the Blaze editor. Inputs: workspace_key, dsl; optional title. Call get_brand_kit first for the brand colors and fonts; search_fonts finds other fonts and search_media or generate_image provide photos. Layout: content in "stack", "row", and "grid" containers and "overlay" anchors is placed automatically and cannot overflow the frame, so no coordinates are needed. Decorative elements in "free" can be placed at exact x/y positions, including partly off the canvas. Pass `dsl` as: { "frames": [ Frame, ... ] } (one frame = one slide; carousels have several) Frame { "w": 1080, "h": 1350, // 4:5 social default (1080x1920 for a story) "pad": 96, // safe-area inset "justify": "center"|"start"|"end"|"between", // vertical placement of the stack "align": "start"|"center", // default horizontal alignment "bg": { "color": } | { "gradient": [,...], "angle": } | { "image": }, "stack": [ Block, ... ], // main content, flows vertically "overlay": [ { "anchor": , "block": Block } ], // pinned to a corner/edge/center "free": [ { "at": { "x": , "y": } | { "region": , "dx": , "dy": }, "block": Block } ] // exact placement for decoration (off-canvas ok) } = top-left|top-right|bottom-left|bottom-right|top-center|bottom-center|center Block (one of): TEXT: { "type": "text", "role": "display"|"title"|"body"|"eyebrow"|"credit", "color": , "text": "..." OR "runs": [ { "t": "...", "color": , "weight": , "italic": , "underline": , "strikethrough": , "caps": } ], "font": , // override the role font with any family (e.g. from search_fonts) "weight": , "tracking": , // thousandths of an em (160 = 0.16em) "autoWidth": , // size the box to ONE line of content — the text (and any // panel) hugs its glyphs instead of filling the column; single-line "panel": { "color": , "opacity": <0..1>, "shape": "box"|"silhouetteRounded"|"callToAction" }? } SHAPE: { "type": "shape", "geo": "rectangle"|"roundedRectangle"|"circle"|"triangle"|"diamond"| "hexagon"|"pill"|"fivePointStar"|... , "w": , "h": , "fill": , "stroke": { "color": , "width": }?, "radius": , "shadow": { "x","y","blur","color","opacity" }? } IMAGE: { "type": "image", "url": , "w": , "h": , "fit": "cover"|"contain", "radius": , // a placed photo card / band (not full-bleed) "stroke": { "color": , "width": }?, "logo": } // logo: true = brand mark GROUP: { "type": "group", "w": , "h": , "layout": "stack"|"row"|"grid", "children": [ Block, ... ] } // moves/rotates as one unit (e.g. a pill = shape + text) ROW: { "type": "row", "gap": , "justify": "start"|"center"|"end", "align": "top"|"middle"|"bottom", "children": [ Block, ... ] } GRID: { "type": "grid", "cols": , "gap": , "children": [ Block, ... ] } SPACE: { "type": "space", "h": } // vertical spacer in a stack Any block also accepts UNIVERSAL props: "rotate": , "opacity": <0..1>, "z": (higher z paints later / on top; use negative z for background decoration). = | { "gradient": [,...], "angle": } = a brand color token from get_brand_kit ("primary", "accent", …, plus "paper" and "ink", which always exist) or any hex such as "#FF006E". Tokens keep the design in the brand palette. RULES: - "role" picks the font automatically (display/title = title font; body/eyebrow/credit = body font). Only set "font" when you deliberately want a different family. - Use "runs" to color one or two key words with an accent color; highlighting more reduces the contrast. - "display" = short headline (about 9 words or fewer). "title" = medium. "body" = supporting copy. - "eyebrow" is ALL-CAPS small (brand mark / kicker / slide number) — usually an overlay (top-left = brand, top-right = "01 / 05"). - Shapes, gradients, rotation and free placement are for art direction — accents, dividers, badges, framing. Keep the composition clean; don't clutter. - Per carousel slide, vary the bg for rhythm and ensure text contrasts its background. For legibility over a busy area, give text a "panel" (e.g. a dark box at ~0.55 opacity). - For a photo: use bg.image for a full-bleed background (get a URL from search_media or generate_image), or a placed "image" block for a card/band inside the layout. Over a photo, keep text in the safe area with high-contrast colors and a panel. - Keep on-image text short. The post caption is set separately. Returns the design id, an editor URL, the element structure (with the aliases the design edit tools use, such as set_design_text and move_design_element), and a rendered preview of every slide. It always creates a new design. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `dsl` (object, required): The design layout: { "frames": [ Frame, ... ] }. See the frame and block format in the tool description. - `title` (string, optional): Optional design title. Defaults to the first line of copy. ## set_design_text Set design text · Can overwrite or delete data Replace the words of one text element in an existing design. The element keeps its font, size, color, and position; the text re-wraps to fit its box. Use it to change a headline, caption, or button label. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `text` (string, required): The new text. ## replace_design_image Replace design image · Can overwrite or delete data; reaches outside Blaze Swap the picture in one image element of an existing design for another image, keeping the element's size and position. The image URL must be publicly reachable, for example a result from search_media or get_generated_image. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `image_url` (string, required): URL of the new image. ## recolor_design_element Recolor design element · Can overwrite or delete data Change the color of one element in an existing design. On a text element it sets the text color. On a shape or a slide background it sets the fill: a solid color, or a gradient. Pass color for a solid color or gradient for a gradient. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `color` (string, optional): The new color: a hex color such as "#1A1A1A" (8-digit #RRGGBBAA for transparency) or a brand color token from get_brand_kit such as "primary". - `gradient` (object, optional): Shapes and backgrounds only: a gradient fill, { "gradient": ["#RRGGBB", ...], "angle": }. ## set_design_font_size Set design font size · Can overwrite or delete data Set the font size of one text element in an existing design, in points. The text re-wraps in its box. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `font_size` (number, required): Size in points, e.g. 64. ## set_design_font_weight Set design font weight · Can overwrite or delete data Set the font weight of one text element in an existing design, for example 400 for regular or 700 for bold. If the element's font doesn't have that weight, the nearest one it has is used and the response says so. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `font_weight` (number, required): Weight, e.g. 400, 600, 700. ## set_design_element_width Set design element width · Can overwrite or delete data Set the width of one element in an existing design, in design pixels; text re-wraps to the new width. Pass "auto" to shrink a text element to fit its text on one line, for example so a button panel fits its label. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `width` (string, required): Width in design pixels (e.g. "840"), or "auto". ## set_design_text_panel Set design text panel · Can overwrite or delete data Add, restyle, or remove the filled panel behind one text element in an existing design, such as a button or a strip that makes text readable over a photo. Pass panel { "shape": "none" } to remove it. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `panel` (object, required): The panel: { "color": a hex color such as "#1A1A1A" (8-digit #RRGGBBAA for transparency); take brand colors as hex values from get_brand_kit, "opacity": 0..1, "shape": "box"|"silhouetteRounded"|"callToAction"|"none" }. ## move_design_element Move design element · Can overwrite or delete data Move one element of an existing design to a new position. x and y are the new top-left corner in design pixels (a 1080x1350 slide runs from 0,0 to 1080,1350); pass either or both. Use the bounding boxes in the design structure to place it. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). - `x` (number, optional): New left edge, in design pixels. - `y` (number, optional): New top edge, in design pixels. ## remove_design_element Remove design element · Can overwrite or delete data Delete one element (text, image, shape, or logo) from an existing design. Nothing else moves; use move_design_element to close the gap. Element aliases are renumbered after a removal, so read the returned structure before the next edit. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `element` (string, required): The element to change: its alias from the design structure ("text-1", "image-1", "bg", "logo", or slide-scoped "s2-text-1"), or its raw id ("shape:..."). ## set_design_background Set design background · Can overwrite or delete data; reaches outside Blaze Set a full-bleed background image on one slide of an existing design, replacing any background image it already has. The image URL must be publicly reachable, for example a result from generate_image or search_media. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `slide` (string, required): The slide to add to: "frame" for a single design, or the slide alias ("s1", "s2", ...) from the design structure. - `image_url` (string, required): URL of the background image. ## add_design_text Add design text · Writes data without deleting any Add a new text element to one slide of an existing design. Place it with x/y/width/height in design pixels, and set its typography with font_family, font_size, font_weight, and color (take the brand fonts and colors from get_brand_kit). Optionally give it a panel behind it, such as a button. Existing elements are not changed. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `slide` (string, required): The slide to add to: "frame" for a single design, or the slide alias ("s1", "s2", ...) from the design structure. - `text` (string, required): The words to add. - `x` (number, optional): Left edge, in design pixels. - `y` (number, optional): Top edge, in design pixels. - `width` (number, optional): Box width, in design pixels. - `height` (number, optional): Box height, in design pixels. - `font_family` (string, optional): Font family. Defaults to Inter. - `font_size` (number, optional): Size in points. Defaults to 48. - `font_weight` (number, optional): Weight, e.g. 400 or 700. Defaults to 400. - `color` (string, optional): Text color: a hex color such as "#1A1A1A" (8-digit #RRGGBBAA for transparency); take brand colors as hex values from get_brand_kit. Defaults to black. - `panel` (object, optional): Optional panel behind the text: { "color": a hex color such as "#1A1A1A" (8-digit #RRGGBBAA for transparency); take brand colors as hex values from get_brand_kit, "opacity": 0..1, "shape": "box"|"silhouetteRounded"|"callToAction" }. ## add_design_shape Add design shape · Writes data without deleting any Add a decorative shape, such as a scrim, divider, or badge, to one slide of an existing design. Placement "front" (the default) puts it on top of the content; "back" puts it just above the slide background, behind the content. Existing elements are not changed. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `slide` (string, required): The slide to add to: "frame" for a single design, or the slide alias ("s1", "s2", ...) from the design structure. - `shape` (object, required): The shape: { "geo": "rectangle"|"roundedRectangle"|"circle"|"pill"|..., "w": , "h": , "x": , "y": , "fill": , ...], "angle": }>, "radius": , "stroke": { "color", "width" }, "rotate": , "opacity": 0..1, "placement": "front"|"back" }. ## add_design_logo Add design logo · Writes data without deleting any Place the workspace's primary brand logo (from its brand kit) on one slide of an existing design. Existing elements are not changed; use move_design_element or set_design_element_width afterwards to adjust it. The change is saved to the design. The response has the updated design structure (element aliases and positions) and a rendered preview. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (from compose_design or generate_post) or the key from a /designs/ URL. - `slide` (string, required): The slide to add to: "frame" for a single design, or the slide alias ("s1", "s2", ...) from the design structure. ## get_design_preview Get design preview · Read-only Get the rendered preview images of an existing design, by design id (the number returned by compose_design, or the key from a /designs/ URL). A single design returns one image; a carousel returns every slide in order. Use it to see a design before editing or scheduling it. A carousel, or a design without a stored preview, is rendered on request. Read-only: the design and the brand kit are not changed. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `design_id` (string, required): The design id (numeric, from compose_design) or its /designs/ key. ## list_reviews_to_reply List reviews to reply to · Read-only List the reviews in a workspace that have no reply yet, lowest star rating first, then newest; reviews without a star rating come last. Each entry has the review id, source, star rating, author name, age, a text excerpt, any reply draft already saved, and whether a reply can be posted from Blaze or has to be written on the review site itself. Covers reviews on Google Business Profile, Facebook, Yelp, Angi, Thumbtack, BBB and Reddit that Blaze has synced, and recent comments on the workspace's Facebook and Instagram posts. Replies can be posted from Blaze only for Google Business Profile reviews and, where enabled, Facebook reviews; comments are listed for reference and must be answered on the platform. Comments on X, LinkedIn, TikTok and YouTube are not covered. Optional: limit (1-50, default 10) and include_comments (default true). Use draft_review_replies to get suggested replies and send_review_reply to post one. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `limit` (integer, optional): Max reviews to return (1-50). Defaults to 10. - `include_comments` (boolean, optional): Also list up to 5 Facebook and Instagram comments from the last 14 days. Defaults to true. ## draft_review_replies Draft review replies · Writes data without deleting any Get suggested replies to one review, in three tones: warm, professional and brief. The first call for a review generates the drafts with an AI model, using the workspace's customer support voice when one is set up, and saves them on the review; later calls return the saved drafts. Drafts for reviews of 1 or 2 stars are marked as needing a careful read before sending. Input: review_id from list_reviews_to_reply. Nothing is posted. Show the drafts to the user, let them pick or edit one, then call send_review_reply with the final text. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `review_id` (integer, required): The review id from list_reviews_to_reply. ## send_review_reply Send review reply · Writes data without deleting any; reaches outside Blaze Post a public reply to one review under the business's name. The reply appears on the review site right away and is visible to anyone. Confirm the exact text with the user before calling this. Input: review_id from list_reviews_to_reply and text (the full reply, up to 4000 characters). Works for Google Business Profile reviews and, where enabled, Facebook reviews. Yelp, Angi, Thumbtack, BBB and Reddit reviews, and reviews that already have a reply, are refused; answer those on the review site. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `review_id` (integer, required): The review id from list_reviews_to_reply. - `text` (string, required): The exact reply to post, as approved by the user. ## get_performance_digest Get performance digest · Read-only Get a short performance report for a workspace's connected social accounts. For each account it reports followers and impressions (Instagram reach, Facebook unique impressions, YouTube views, Google Business Profile profile views) for yesterday, the trailing 7 days, and the trailing 30 days, all ending yesterday in the workspace's timezone. Each window is compared with the preceding window of the same length. Followers show the latest total and the net adds in each window. Inputs: workspace_key; optional period ("daily" or "weekly", default "daily"; weekly also lists up to 5 top posts published in the last 7 days); optional goal_net_followers_per_day (compares the trailing 7-day average of net adds with the goal). Metrics are collected once a day and can lag or have gaps. Missing values are shown as "—" (null in structured content) with a dated note; they are never estimated. An impressions window is missing if any of its days is missing. Follower net adds only need the totals on the window's first and last days, so they are still shown when days in between are missing, and the note lists those days. Read-only. Parameters: - `workspace_key` (string, required): Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. - `period` (string, optional): 'daily' (default) or 'weekly'. Weekly adds the week's top posts. One of: daily, weekly. - `goal_net_followers_per_day` (number, optional): Optional target for net new followers per day across all accounts.