Frontify

Use this when you need to create a new folder for organizing assets hierarchically. Folders can be created in libraries, projects, or nested within other folders.

frontify_create_folder

Use this when you need to create a new project within a Frontify brand. Projects are collaborative spaces for file management and team work.

frontify_create_project

Use this when you need to permanently delete a comment or reply from a Frontify asset. This also removes any replies under a deleted top-level comment.

frontify_delete_asset_comment

Render one or more Frontify assets (by `ids`) as a widget for the USER to view — this is the only way to download an asset or open it on Frontify. It does NOT return asset data back to you, so never call it to inspect or reason over an asset; for metadata use frontify_get_assets_data. Not a prerequisite for other tools: if you already have an asset id, pass it straight to the tool that needs it.

frontify_display_assets

Render one or more Frontify creative templates (by `ids`) as a widget for the USER to view, with inline detail and AI-assisted customization. It does NOT return template data back to you, so never call it to inspect a template or read its variables; for that use frontify_get_templates_data. Not a prerequisite for exporting: if you already have a template id, pass it straight to frontify_export_creative.

frontify_display_templates

Use this when you need to generate a design from a creative template with custom variable values. Starts an async export job. Use frontify_get_creative_export to check status and get download URLs. Variables can include text, images (asset IDs), and colors. When exporting make sure you come up with unique human readable title based on the variables used for the exported asset.

frontify_export_creative

Use this when you need to generate Frontify URLs for navigation with an agent. Generates URLs for brands, libraries, guidelines, projects, assets, and other Frontify resources. Returns a complete URL that can be used to navigate to the specified resource in the Frontify web application.

frontify_generate_url

Use this when you need to view comments (annotations) on a Frontify asset. Returns comment content, creator, creation date, resolution status, position markings (for visual annotations), mentioned users, and threaded replies. Supports filtering by status (ALL, OPEN, RESOLVED).

frontify_get_asset_comments

Fetch metadata for Frontify assets you already have IDs for (via `ids`), selecting only the `properties` you need. Renders no widget — use it to reason over data, not to present assets. To let the user view/download/open them, pass the same IDs to frontify_display_assets. For visual analysis, request the `asset` group and pass `previewUrl`s to frontify_read_asset.

frontify_get_assets_data

Use this when you need detailed information about a specific Frontify brand. Returns brand details including all associated libraries and projects. Requires the brand ID from frontify_list_brands.

frontify_get_brand

Use this when you need the colors of a specific brand color palette (the brand essentials colors). Returns the palette with its color list and all available color-format representations (hex, RGBA, CMYK, HSL, LAB, color system / Pantone). The color list is paginated via the page/limit parameters — check hasNextPage and request further pages to retrieve every color. Requires the palette ID from frontify_list_brand_color_palettes. Contextual usage information about colors (e.g. when and how to apply them) is documented in the brand's guidelines — use frontify_list_guidelines to find them.

frontify_get_brand_color_palette

Use this when you need a brand's defined font families (the brand essentials fonts). Returns each family with its CSS name, provider (Adobe, Google, Monotype, self-hosted) and provider-specific font styles (Adobe kitId, Monotype fontId/cssUrl, self-hosted formats). Requires the brand ID from frontify_list_brands. Contextual usage information about fonts (e.g. when and how to apply them) is documented in the brand's guidelines — use frontify_list_guidelines to find them.

frontify_get_brand_font_families

Use this when you need to find users who have access to a Frontify library or project — pass whichever ID you have and the scope is resolved automatically. Returns user IDs, names, emails, and roles. Essential for finding user IDs to mention in comments (write @ followed by user colon and the user ID in square brackets).

frontify_get_collaborators

Retrieve assets from a Frontify collection, filterable by term. Returns a lightweight, paginated list (id/type/title/previewUrl), no widget. Pass the ids to frontify_display_assets to view/download/open them, or to frontify_get_assets_data for more metadata.

frontify_get_collection_assets

Use this when you need to check the status of a creative export job and retrieve download URLs. Jobs have statuses: PROCESSING, RENDERING, FINISHED, FAILED, CANCELED. Poll this after calling frontify_export_creative.

frontify_get_creative_export

Use this when you need to identify the currently authenticated Frontify user. Returns user ID, email, name, and avatar URL. Useful for personalizing responses or verifying user context.

frontify_get_current_user

Browse a folder in a library or project. Returns subfolders and a lightweight asset list (id/type/title/previewUrl), no widget. Pass asset ids to frontify_display_assets to view/download/open them, or to frontify_get_assets_data for more metadata. Get root folder IDs from frontify_get_library or frontify_get_project, then drill into subfolders here.

frontify_get_folder_contents

Use this when you need detailed information about a specific guideline, including its library pages (asset collections) and guideline pages (documentation pages). The guideline pages list is paginated via the page/limit parameters. Returns page structure for further exploration.

frontify_get_guideline

Use this when you need to read the content of a guideline page. Returns the whole page as Markdown: `##` headings, the text of each content block, `---` where the page has a divider, and one `` line per image (already downsized to a reasonable preview resolution). Pass those previewUrl values to frontify_read_asset for closer visual analysis when the text alone does not answer the question (e.g. logo clear-space diagrams, do's-and-don'ts panels, color charts). Rich text keeps its formatting, so bold, links and lists in the source survive. A do's-and-don'ts block is split into `Do:` and `Don't:` lists — read those labels carefully, because the recommendation and the anti-recommendation are opposites. A callout is rendered as a `>` blockquote. A block Frontify cannot render to text is marked `(no readable text)`. An older, unstructured block type is prefixed with its `**Block Name**` so you know what kind of content you could not fully read.

frontify_get_guideline_page

Use this when you need to explore a Frontify library structure. Returns folders, assets, collections, licenses, and custom metadata property definitions. Essential for understanding available metadata options before using frontify_update_assets, and the source of the collection, license and custom-metadata property ids that frontify_search_assets filters accept.

frontify_get_library

Retrieve assets from a library page within a guideline, filterable by term. Returns a lightweight, paginated list (id/type/title/previewUrl), no widget. Pass the ids to frontify_display_assets to view/download/open them, or to frontify_get_assets_data for more metadata.

frontify_get_library_page_assets

Use this when you need to explore a Frontify project structure. Returns folders and assets. Projects are collaborative spaces for file management.

frontify_get_project

Use this when you need to retrieve the available targets from the Frontify account. Targets are used to categorize assets for specific use cases or channels (e.g., Web, Print, Social Media).

frontify_get_targets

Fetch full data for Frontify creative templates you already have IDs for (via `ids`): variables that are connected to design elements (with their keys, types, and current values), export options, pages, and preview URLs. Renders no widget — use it to reason over a template before exporting. Image variables expect the full asset ID. To let the user view templates, pass the same IDs to frontify_display_templates; to generate a design, use frontify_export_creative.

frontify_get_templates_data

Use this to discover available workflow statuses for a library. Returns the list of status IDs, names, and colors that can be passed as workflowStatus.id to frontify_update_assets. A library must have a workflow configured to return statuses.

frontify_get_workflow_statuses

Use this when you need to discover a brand's color palettes (the brand essentials colors). Returns a paginated list of palette summaries — id, name, description, and colorCount — without color data. To fetch the actual colors of a specific palette, pass its id directly to frontify_get_brand_color_palette. Requires the brand ID from frontify_list_brands. Contextual usage information about colors (e.g. when and how to apply them) is documented in the brand's guidelines — use frontify_list_guidelines to find them.

frontify_list_brand_color_palettes

Use this when you need to discover all available brands in the Frontify account. Returns brand IDs, names, slugs, avatars, and colors. This is typically the first step to navigate the Frontify hierarchy.

frontify_list_brands

Use this when you need to discover all available creative templates in a brand. Returns template names, IDs, preview images, and basic metadata. Templates can be used to generate on-brand designs programmatically. Renders no widget — to let the user view templates, pass their IDs to frontify_display_templates; for full template data (variables, export options), use frontify_get_templates_data.

frontify_list_creative_templates

Use this when you need to discover all available guidelines for a Frontify brand. Returns guideline names, IDs, colors, and URLs. Guidelines are brand portals containing documentation and style guides.

frontify_list_guidelines

Use this when you need to relocate assets to a different folder within the same library or workspace. This changes the asset location permanently. Only moves within the same library/workspace are supported.

frontify_move_assets

Visually analyze Frontify assets. Pass Frontify CDN `previewUrl`(s) — from the search/listing tools or from frontify_get_assets_data (request the `asset` group) — and it returns the images as inline content for analysis (e.g. auto-tagging, guideline interpretation). Only Frontify CDN URLs are accepted.

frontify_read_asset

Use this when you need to remove specific targets from one or more assets. Only the specified targets are removed - other targets on the assets remain unchanged.

frontify_remove_asset_targets

Use this when you need to remove a checklist item from a workflow task.

frontify_remove_workflow_checklist_item

Find assets inside a Frontify library, project, or an entire brand — pass whichever ID you have and the scope is resolved automatically. Libraries and projects support advanced filtering (tags, collections, dates, custom metadata, workflow status, orientation, extension, licenses and more), sorting, and folder scoping; a brand ID supports only a search term, and passing filters/folderId/isRecursive with one is rejected rather than silently ignored. There is no asset-type filter — approximate "images only" with an extension filter. Results are paginated by cursor, NOT by page: pass the returned nextCursor back to get more. No total count is available in any scope. Pass the ids to frontify_display_assets to view/download/open them, or to frontify_get_assets_data for more metadata.

frontify_search_assets

Use this to update asset metadata — titles, descriptions, alternative text, copyright, tags, workflow statuses, custom metadata, licenses and collections. Handles one asset or many: pass a one-entry `assets` array for a single asset, or an entry per asset to give each its own values in one call. All assets must live in the same library. Up to 500 assets per call. Only send the fields you want to change: an omitted field is left untouched, while an explicit null clears it. To add many assets to the same collection, give every asset its own entry with the same value, e.g. `assets: [{id: "a1", data: {addCollections: ["c1"]}}, {id: "a2", data: {addCollections: ["c1"]}}]` — the cardinality is per-asset, not per-collection. Known limitation: `customMetadata` has no support for CATALOG-type properties (only text/number/date/optionIds). Assets and individual fields fail independently — read "status" and "failedAssets" in the result, because an asset can appear in both "updatedAssets" and "failedAssets" when only some of its fields applied.

frontify_update_assets

Use this when you need to update an existing workflow checklist item (content, assignee, or completion state).

frontify_update_workflow_checklist_item

Step 1 of 3 for uploading a local file to Frontify. Returns an id and a list of presigned upload urls. Step 2 (you perform this yourself): upload the file bytes by sending an HTTP PUT request to each of the presigned urls with the raw file content as the body of an HTTP PUT request to that URL. For a single-chunk file there is one URL. Step 3: call frontify_create_asset with the returned id as the fileId to finalize and create the asset. IMPORTANT: step 2 requires you to make an outbound HTTP PUT to a storage domain. If your environment restricts network egress (many agent sandboxes do), this PUT will fail — in that case host the file at a public http/https URL and use frontify_create_asset_from_url instead, which performs all three steps server-side.

frontify_upload_file