Metadata MCP Connector

Update Brand Kit

update_brand_kit

Destructive

Update existing brand kit with brand DNA parameters. Only company_url is required; all others are optional.

Input Schema

Name	Required	Description
`dos`	No	Brand 'do' rules.
`tone`	No	Brand tone description.
`donts`	No	Brand 'don't' rules.
`fonts`	No	Legacy flat font list. Each: {name, type}. Layered creatives do not read it: use headline_font and body_font.
`colors`	No	Legacy flat color list. Each: {hex (with #), type, name?}.
`tagline`	No	Primary brand tagline.
`cta_font`	No	CTA/button font family. Layered creatives do not read it: their CTA uses body_font.
`cta_size`	No	CTA/button font size.
`logo_url`	No	Direct URL to a single company logo image (back-compat; prefer logo_urls). Setting a permanent brand logo requires elevated Metadata permissions.
`body_font`	No	Body text font family. Layered creatives set the supporting line, the CTA and any other text in it.
`body_size`	No	Body text font size.
`logo_urls`	No	One or more direct URLs to logo images to set as the brand's permanent logo(s). Each uploaded logo is automatically expanded into clean, persisted variants (transparent, high-res, and both a light and dark version when the mark is a single color) so generated creatives have multiple usable options. Setting a permanent brand logo requires elevated Metadata permissions.
`cta_weight`	No	CTA/button font weight.
`body_weight`	No	Body text font weight.
`clear_logos`	No	Remove the brand kit's permanent logo override entirely (no logo_url needed), so creatives fall back to the cached Brandfetch logo variants for the domain. Use when a manually set logo turned out wrong or low quality. Same elevated Metadata permissions as setting one.
`company_url`	Yes	Company website URL or domain (e.g. 'ambient.ai').
`logo_misuse`	No	List of logo misuse rules.
`button_shape`	No	Button shape description.
`eyebrow_case`	No	Eyebrow text case rule.
`eyebrow_font`	No	Eyebrow font family. Layered creatives do not read it: use body_font.
`logo_on_dark`	No	Logo color rule on dark backgrounds.
`primary_font`	No	Primary font family name. Layered creatives use it where headline_font or body_font is unset.
`proof_points`	No	Evidence/social proof items.
`accent_colors`	No	Accent color palette.
`cta_linespace`	No	CTA/button line spacing.
`cta_placement`	No	CTA placement guidance.
`headline_case`	No	Headline text case rule.
`headline_font`	No	Headline font family. Layered creatives set the headline in it.
`headline_size`	No	Headline font size range.
`logo_on_light`	No	Logo color rule on light backgrounds.
`product_names`	No	Product name mapping (e.g. {platform: 'X', vlm: 'Y'}).
`standard_ctas`	No	Standard CTA labels.
`subtitle_font`	No	Subtitle font family. Layered creatives do not read it: their supporting line uses body_font.
`visual_motifs`	No	Brand visual motifs.
`body_linespace`	No	Body text line spacing.
`button_padding`	No	Button padding.
`eyebrow_weight`	No	Eyebrow font weight.
`primary_colors`	No	Primary color palette.
`secondary_font`	No	Secondary/display font family name. Layered creatives do not read it: use headline_font or body_font.
`channel_display`	No
`cta_letterspace`	No	CTA/button letter spacing.
`headline_weight`	No	Headline font weight.
`primary_layouts`	No	Layout system definitions.
`search_keywords`	No	SEO/search keywords for the brand.
`semantic_colors`	No	Semantic/status colors.
`subtitle_weight`	No	Subtitle font weight.
`body_letterspace`	No	Body text letter spacing.
`button_text_case`	No	Button text case.
`channel_facebook`	No
`channel_linkedin`	No
`extended_palette`	No	Extended grayscale palette.
`logo_clear_space`	No	Logo clear space rule.
`long_description`	No	Company description for marketing use.
`remove_old_logos`	No	When true (default), replace the brand's existing logos with the provided ones; when false, append to them.
`secondary_colors`	No	Secondary (supporting) color palette.
`tagline_variants`	No	Alternative taglines.
`button_background`	No	Button background style.
`button_text_color`	No	Button text color rule.
`eyebrow_linespace`	No	Eyebrow line spacing.
`headline_formulas`	No	Headline writing patterns.
`photography_avoid`	No	Photography anti-patterns.
`photography_style`	No	Photography style description.
`tagline_placement`	No	Tagline placement guidance.
`button_text_weight`	No	Button text weight.
`headline_linespace`	No	Headline line spacing.
`primary_font_usage`	No	Primary font usage description.
`subtitle_linespace`	No	Subtitle line spacing.
`value_propositions`	No	Core value propositions.
`website_background`	No	6-digit hex color (e.g. '#FFFFFF') of the brand website's background. generate_brand_creative uses it as the default dominant background for ads (use_website_background). Set it when the user wants ads to match their site's background or the auto-detected value is wrong.
`eyebrow_letterspace`	No	Eyebrow letter spacing.
`headline_letterspace`	No	Headline letter spacing.
`photography_subjects`	No	Recommended photo subjects.
`promotional_elements`	No	Promotional proof points.
`secondary_font_usage`	No	Secondary font usage description.
`subtitle_letterspace`	No	Subtitle letter spacing.
`photography_treatment`	No	Photo treatment rules.
`content_hierarchy_order`	No	Content element ordering.
`content_hierarchy_spacing`	No	Section spacing guidance.
`content_hierarchy_text_max_width`	No	Max text block width.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 25, 2026

addedInput schema / properties / channel_display / additionalProperties
```
Added value: +true
```
removedInput schema / properties / channel_display / description
```
Removed value: -"Display ads channel config."
```

addedInput schema / properties / channel_display / properties

Added value: +{
+  "cta_preference": {
+    "type": "string"
+  },
+  "focus": {
+    "type": "string"
+  },
+  "size": {
+    "type": "string"
+  },
+  "text_overlay_limit": {
+    "type": "string"
+  }
+}

addedInput schema / properties / channel_facebook / additionalProperties
```
Added value: +true
```
removedInput schema / properties / channel_facebook / description
```
Removed value: -"Facebook channel config."
```

addedInput schema / properties / channel_facebook / properties

Added value: +{
+  "cta_preference": {
+    "type": "string"
+  },
+  "focus": {
+    "type": "string"
+  },
+  "size": {
+    "type": "string"
+  },
+  "text_overlay_limit": {
+    "type": "string"
+  }
+}

addedInput schema / properties / channel_linkedin / additionalProperties
```
Added value: +true
```
removedInput schema / properties / channel_linkedin / description
```
Removed value: -"LinkedIn channel config."
```

addedInput schema / properties / channel_linkedin / properties

Added value: +{
+  "cta_preference": {
+    "type": "string"
+  },
+  "focus": {
+    "type": "string"
+  },
+  "size": {
+    "type": "string"
+  },
+  "text_overlay_limit": {
+    "type": "string"
+  }
+}

addedInput schema / properties / primary_layouts / items / additionalProperties
```
Added value: +true
```

addedInput schema / properties / primary_layouts / items / properties

Added value: +{
+  "background": {
+    "type": "string"
+  },
+  "best_for": {
+    "type": "string"
+  },
+  "frequency": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "structure": {
+    "type": "string"
+  },
+  "text_alignment": {
+    "type": "string"
+  }
+}

addedInput schema / properties / product_names / additionalProperties
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedSep 25, 2026

addedInput schema / properties / secondary_colors

Added value: +{
+  "description": "Secondary (supporting) color palette.",
+  "items": {
+    "properties": {
+      "hex": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "usage": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "hex",
+      "name",
+      "usage"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed8 schema fields changedSep 24, 2026

changedInput schema / properties / body_font / description

Previous value: -"Body text font family."New value: +"Body text font family. Layered creatives set the supporting line, the CTA and any other text in it."

changedInput schema / properties / cta_font / description

Previous value: -"CTA/button font family."New value: +"CTA/button font family. Layered creatives do not read it: their CTA uses body_font."

changedInput schema / properties / eyebrow_font / description

Previous value: -"Eyebrow font family."New value: +"Eyebrow font family. Layered creatives do not read it: use body_font."

changedInput schema / properties / fonts / description

Previous value: -"Legacy flat font list. Each: {name, type}."New value: +"Legacy flat font list. Each: {name, type}. Layered creatives do not read it: use headline_font and body_font."

changedInput schema / properties / headline_font / description

Previous value: -"Headline font family."New value: +"Headline font family. Layered creatives set the headline in it."

changedInput schema / properties / primary_font / description

Previous value: -"Primary font family name."New value: +"Primary font family name. Layered creatives use it where headline_font or body_font is unset."

changedInput schema / properties / secondary_font / description

Previous value: -"Secondary/display font family name."New value: +"Secondary/display font family name. Layered creatives do not read it: use headline_font or body_font."

changedInput schema / properties / subtitle_font / description

Previous value: -"Subtitle font family."New value: +"Subtitle font family. Layered creatives do not read it: their supporting line uses body_font."

First observedSep 16, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds only required/optional framing and does not explain partial-update semantics, whether omitted fields are preserved, or the impact of the destructive mutation.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the core action and followed by the key required/optional distinction. There is no wasted language.

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

Completeness2/5

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

This is a high-complexity mutation tool with 79 parameters, no output schema, and a destructive annotation. The description is too sparse to explain update semantics, destructive behavior, or operational context beyond basic required/optional information.

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 96%, so parameter semantics are largely documented by the schema itself. The description only restates that company_url is required and all others are optional, adding little beyond the structured parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: update an existing brand kit with brand DNA parameters. The word 'existing' helps distinguish it from generate_brand_kit, but it does not explicitly name sibling alternatives or scope what kinds of updates are supported.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It only states that company_url is required and others are optional, with no guidance on when to use this tool versus generate_brand_kit, get_brand_kit, or edit_brand_creative. There are no exclusions, prerequisites, or warnings about destructive updates.

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

All Metadata MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?