Skip to main content
Glama

Update brand settings

flypost_update_brand_kit
Destructive

Change the project's brand settings (Project Settings > Brand), only the fields you pass: company and audience, website, industry, products, key topics, brand colours (#RRGGBB), fonts, the infographic visual tone, visual notes for image generation, and the carousel logo settings. Every generator reads these, so change them only when the user asks or confirms (e.g. "we now sell to CFOs", "our accent colour is #FF5A1F"). Read flypost_get_brand_kit first. Logos are filed with flypost_upload_logo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flypost_update_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontsNo
colorsNo#RRGGBB values; only the ones you pass change.
websiteNo
industryNo
productsNoReplaces the product list.
key_topicsNoReplaces the key topics.
project_idNoProject (workspace) id. Omit to use the active project set with flypost_use_project.
company_nameNo
target_audienceNo
visual_tone_notesNoFree-text art direction the image generators follow.
carousel_show_logoNo
carousel_logo_scaleNo
product_descriptionNo
infographic_visual_toneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag this as a mutation with destructiveHint=true; the description adds the crucial mitigation that it is a partial update ('only the fields you pass') and discloses the blast radius ('Every generator reads these'), which explains why careless edits are risky. It stops short of stating that top-level list fields such as products and key_topics are wholesale replacements — that fact lives only in the schema description, not the prose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and partial-update rule, followed by the risk rationale, then the prerequisites. The long field enumeration is dense but each item earns its place by mapping a parameter; the parenthetical menu path is slightly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter destructive mutation with no output schema, the definition covers what changes, when to change it, downstream consumers, and the read-before-write and logo-handling alternatives. Missing only edge details like merge behaviour for nested objects and what a partial success looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 36% across 14 parameters, but the description compensates by enumerating nearly every top-level field an agent can set, including the colour format (#RRGGBB) and the nature of the infographic tone choice. It omits the project_id default behaviour and the carousel_logo_scale bounds, which the schema covers on its own.

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?

States a specific verb and resource ('Change the project's brand settings') and scopes it to the exact field groups affected (company/audience, website, industry, products, key topics, colours, fonts, infographic tone, visual notes, carousel logo). It also disambiguates from siblings in both directions: read flypost_get_brand_kit first, and use flypost_upload_logo for logos.

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?

Gives an explicit when-to-use condition ('change them only when the user asks or confirms') with concrete triggering examples ('we now sell to CFOs', 'our accent colour is #FF5A1F'), plus a mandatory prerequisite (read flypost_get_brand_kit first) and a routing rule to flypost_upload_logo for logo files.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.