Skip to main content
Glama

Create a brand

create_brand

[writes flayr data · write scope] Creates a new brand in the account owner's organization, the same as "New brand" in the dashboard. Send name and optionally website, like { name: "Dragon Shop", website: "https://shop.example.com" }. Only an ACCOUNT-WIDE connection with the write scope can do this; a connection bound to one brand gets 403. The plan's brand limit applies: at the limit the call is a 402 and nothing is created (relay the message). Optional profile, voice, colors and fonts (the brand_profile_update shapes) and logoStorageId (an image from upload_media) are saved in the same call. Full description and schema: describe_tool {"name":"create_brand"}. (Wraps POST /api/v2/brands.)

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": {
      "name": "<name>"
    },
    "name": "create_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFormat: string; e.g. "Summer launch". The brand name. Must not match another active brand in the organization.
fontsNoFormat: object; e.g. {"heading":"Inter"}. Font family names. A role left out keeps its stored font. At least one is required. Fields: heading, body.
orgIdNoFormat: string; e.g. "orgId_123". The organization to create in.
voiceNoFormat: object; e.g. {"name":"Summer launch"}. The brand default voice. Created (as the default) when the brand has none. Fields: name, tone, style, targetAudience, keywords, avoidWords, ….
colorsNoFormat: object; e.g. {"primary":"#112233"}. Fields: primary, secondary, palette.
profileNoFormat: object; e.g. {"companyName":"Example Studio"}. Only the fields sent are changed. Fields: companyName, tagline, mission, industry, website, competitors, ….
websiteNoFormat: string; e.g. "https://example.com". The brand's website. Shortcut for profile.website.
logoStorageIdNoFormat: string; e.g. "logoStorageId_123". A storageId from POST /api/v2/media/upload-url (an image). It becomes the brand's primary logo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / fonts / description
      Previous value: -"Format: object; e.g. {\"heading\":\"Inter\"}. Font family names. Fields: heading, body."New value: +"Format: object; e.g. {\"heading\":\"Inter\"}. Font family names. A role left out keeps its stored font. At least one is required. Fields: heading, body."
    • changedInput schema / properties / logoStorageId / description
      Previous value: -"Format: string; e.g. \"logoStorageId_123\"."New value: +"Format: string; e.g. \"logoStorageId_123\". A storageId from POST /api/v2/media/upload-url (an image). It becomes the brand's primary logo."
    • changedInput schema / properties / name / description
      Previous value: -"Format: string; e.g. \"Summer launch\". The brand name."New value: +"Format: string; e.g. \"Summer launch\". The brand name. Must not match another active brand in the organization."
    • changedInput schema / properties / orgId / description
      Previous value: -"Format: string; e.g. \"orgId_123\"."New value: +"Format: string; e.g. \"orgId_123\". The organization to create in."
    • changedInput schema / properties / profile / description
      Previous value: -"Format: object; e.g. {\"companyName\":\"Example Studio\"}. Fields: companyName, tagline, mission, industry, website, competitors, …."New value: +"Format: object; e.g. {\"companyName\":\"Example Studio\"}. Only the fields sent are changed. Fields: companyName, tagline, mission, industry, website, competitors, …."
    • changedInput schema / properties / voice / description
      Previous value: -"Format: object; e.g. {\"name\":\"Summer launch\"}. Fields: name, tone, style, targetAudience, keywords, avoidWords, …."New value: +"Format: object; e.g. {\"name\":\"Summer launch\"}. The brand default voice. Created (as the default) when the brand has none. Fields: name, tone, style, targetAudience, keywords, avoidWords, …."
    • changedInput schema / properties / website / description
      Previous value: -"Format: string; e.g. \"https://example.com\"."New value: +"Format: string; e.g. \"https://example.com\". The brand's website. Shortcut for profile.website."
  2. Changed15 schema fields changed
    • changedInput schema / properties / colors / description
      Previous value: -"REPLACES the brand palette, the same as saving Brand → Overview → Brand Colors: the stored list is primary, secondary, then palette (duplicates dropped); primary and secondary are its top two. 6-digit hex, `#` optional, stored lower case."New value: +"Format: object; e.g. {\"primary\":\"#112233\"}. Fields: primary, secondary, palette."
    • removedInput schema / properties / colors / properties
      Removed value: -{
      -  "palette": {
      -    "description": "Further brand colors, in order.",
      -    "items": {
      -      "pattern": "^#?[0-9a-fA-F]{6}$",
      -      "type": "string"
      -    },
      -    "maxItems": 16,
      -    "type": "array"
      -  },
      -  "primary": {
      -    "pattern": "^#?[0-9a-fA-F]{6}$",
      -    "type": "string"
      -  },
      -  "secondary": {
      -    "pattern": "^#?[0-9a-fA-F]{6}$",
      -    "type": "string"
      -  }
      -}
    • removedInput schema / properties / colors / required
      Removed value: -[
      -  "primary"
      -]
    • changedInput schema / properties / fonts / description
      Previous value: -"Font family names. A role left out keeps its stored font. At least one is required."New value: +"Format: object; e.g. {\"heading\":\"Inter\"}. Font family names. Fields: heading, body."
    • removedInput schema / properties / fonts / properties
      Removed value: -{
      -  "body": {
      -    "maxLength": 100,
      -    "type": "string"
      -  },
      -  "heading": {
      -    "maxLength": 100,
      -    "type": "string"
      -  }
      -}
    • changedInput schema / properties / logoStorageId / description
      Previous value: -"A storageId from POST /api/v2/media/upload-url (an image). It becomes the brand's primary logo."New value: +"Format: string; e.g. \"logoStorageId_123\"."
    • changedInput schema / properties / name / description
      Previous value: -"The brand name. Must not match another active brand in the organization."New value: +"Format: string; e.g. \"Summer launch\". The brand name."
    • removedInput schema / properties / name / maxLength
      Removed value: -200
    • changedInput schema / properties / orgId / description
      Previous value: -"The organization to create in. Needed only when the key owner belongs to more than one: without it the call is a 422 (code ORG_REQUIRED) that lists them."New value: +"Format: string; e.g. \"orgId_123\"."
    • changedInput schema / properties / profile / description
      Previous value: -"Only the fields sent are changed. Unknown fields are a 422."New value: +"Format: object; e.g. {\"companyName\":\"Example Studio\"}. Fields: companyName, tagline, mission, industry, website, competitors, …."
    • removedInput schema / properties / profile / properties
      Removed value: -{
      -  "brandValues": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "companyName": {
      -    "maxLength": 200,
      -    "type": "string"
      -  },
      -  "competitors": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "contentPillars": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "hashtagSets": {
      -    "items": {
      -      "properties": {
      -        "name": {
      -          "type": "string"
      -        },
      -        "tags": {
      -          "items": {
      -            "type": "string"
      -          },
      -          "type": "array"
      -        }
      -      },
      -      "required": [
      -        "name",
      -        "tags"
      -      ],
      -      "type": "object"
      -    },
      -    "maxItems": 20,
      -    "type": "array"
      -  },
      -  "industry": {
      -    "maxLength": 200,
      -    "type": "string"
      -  },
      -  "mission": {
      -    "maxLength": 4000,
      -    "type": "string"
      -  },
      -  "tagline": {
      -    "maxLength": 200,
      -    "type": "string"
      -  },
      -  "targetDemographics": {
      -    "properties": {
      -      "ageRanges": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "gender": {
      -        "type": "string"
      -      },
      -      "interests": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "location": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "painPoints": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  "website": {
      -    "maxLength": 200,
      -    "type": "string"
      -  }
      -}
    • changedInput schema / properties / voice / description
      Previous value: -"The brand default voice. Created (as the default) when the brand has none."New value: +"Format: object; e.g. {\"name\":\"Summer launch\"}. Fields: name, tone, style, targetAudience, keywords, avoidWords, …."
    • removedInput schema / properties / voice / properties
      Removed value: -{
      -  "avoidWords": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "exampleLinks": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "examplePosts": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "guide": {
      -    "maxLength": 30000,
      -    "type": "string"
      -  },
      -  "keywords": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "name": {
      -    "type": "string"
      -  },
      -  "sampleContent": {
      -    "type": "string"
      -  },
      -  "style": {
      -    "type": "string"
      -  },
      -  "targetAudience": {
      -    "type": "string"
      -  },
      -  "tone": {
      -    "type": "string"
      -  }
      -}
    • changedInput schema / properties / website / description
      Previous value: -"The brand's website. Shortcut for profile.website."New value: +"Format: string; e.g. \"https://example.com\"."
    • removedInput schema / properties / website / maxLength
      Removed value: -200
  3. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description still adds substantial non-annotation context: the 403 scope failure mode, the 402 plan-limit behavior with 'nothing is created', and the add-on shapes saved in the same call. It does not describe what a successful response returns, though the failure semantics are unusually well disclosed.

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?

Front-loaded with a scope tag and the core action, then prerequisites and limits, then optional-field guidance. Dense but nearly every clause carries information; the parenthetical '(Wraps POST /api/v2/brands.)' and the describe_tool pointer are the only borderline-filler items.

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

Completeness3/5

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

For an eight-parameter creation tool with nested objects, the description covers preconditions, side effects, and optional-field provenance well. Since no output schema exists, the description should state what a successful call returns (e.g. the created brand object and its id), and that omission is the main completeness gap.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all eight parameters including nested field lists. The description adds meaningful cross-references — that profile/voice/colors/fonts follow the brand_profile_update shapes and that logoStorageId must come from upload_media — plus a concrete example payload. That is real added meaning beyond the schema, though not exhaustive.

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 ('Creates a new brand in the account owner's organization') and anchors it to a known dashboard action ('the same as "New brand"'). It implicitly separates itself from list_brands/brand_profile_get by framing this as creation, and clarifies that profile/voice/colors/fonts are applied in the same call rather than requiring a follow-up update.

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?

Explicit prerequisites are given: only an ACCOUNT-WIDE connection with write scope works, and a brand-bound connection yields 403. It also flags the plan brand limit and the resulting 402 with the instruction to relay the message, and points to upload_media as the source for logoStorageId. Alternative paths (describe_tool for full schema) are named.

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.

Resources