easysociable-mcp

Create brand

create_brand

Create a new owner-scoped brand kit to define typography, colors, handle, and optional logo, ensuring a consistent visual identity for slideshows.

Instructions

Create a new owner-scoped Brand kit defining typography, color palette, handle, and optional logo asset. Call before creating slideshow runs to establish consistent visual identity. Do NOT use to edit an existing brand; use update_brand instead. Requires workspace owner authorization. Persists initial brand record with revision 1. Returns created Brand entity with brandId and initial revision.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Canonical brand name (e.g. Acme Corp).
`colors`	No	Color palette tokens (primary, secondary, accent, surface, text).
`handle`	No	Social media handle (e.g. @acme).
`typography`	No	Typography settings (headingFont, bodyFont).
`displayName`	No	User-facing display name.
`logoAssetId`	No	Optional image asset ID for brand logo.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`brandId`	No	Created brand ID.
`revision`	No	Initial revision (1).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "brandId": {
+      "description": "Created brand ID.",
+      "type": "string"
+    },
+    "revision": {
+      "description": "Initial revision (1).",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed6 schema fields changedv0.1.16Oct 5, 2026
- addedInput schema / properties / colors / description
```
Added value: +"Color palette tokens (primary, secondary, accent, surface, text)."
```
- addedInput schema / properties / displayName / description
```
Added value: +"User-facing display name."
```
- addedInput schema / properties / handle / description
```
Added value: +"Social media handle (e.g. @acme)."
```
- addedInput schema / properties / logoAssetId / description
```
Added value: +"Optional image asset ID for brand logo."
```
- addedInput schema / properties / name / description
```
Added value: +"Canonical brand name (e.g. Acme Corp)."
```
- addedInput schema / properties / typography / description
```
Added value: +"Typography settings (headingFont, bodyFont)."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description goes further by disclosing the owner-authorization requirement, that the initial record is persisted at revision 1, and what the created entity returns. It adds real behavioral context rather than restating the annotations.

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?

Five short sentences, front-loaded with purpose and followed by sequencing, exclusion, and preconditions in priority order. Each sentence earns its place, though the return-value sentence is somewhat redundant given an output schema exists.

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

Completeness5/5

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

For a mutation tool with nested-object parameters and an output schema, the description covers purpose, sequencing, exclusion, authorization, and persistence semantics. An agent has everything needed to call it correctly without consulting siblings.

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 every parameter is already documented in the schema; the baseline is 3. The description restates the categories of fields (typography, colors, handle, optional logo) without adding format, constraint, or default details beyond what the schema provides.

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 ("Create a new owner-scoped Brand kit") and enumerates what the entity defines (typography, color palette, handle, optional logo asset). This is easily distinguished from update_brand, delete_brand, and the other brand siblings.

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 explicit sequencing guidance ("Call before creating slideshow runs to establish consistent visual identity"), an explicit exclusion with the correct alternative ("Do NOT use to edit an existing brand; use update_brand instead"), and a precondition (workspace owner authorization). Nothing is left to inference.

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