easysociable-mcp

Get brand

get_brand

Read-onlyIdempotent

Retrieve a brand profile by brandId, including palette, typography, logo, and revision, to inject brand styles before generating or updating branded slides.

Instructions

Fetch a complete Brand profile by brandId, including typography tokens, 4-color palette (primary, secondary, accent, surface), logoAssetId, and baseRevision. Call before generating or updating branded slides to inject brand styles and capture baseRevision. Alternatives: Use list_brands to discover brandIds. Read-only query scoped to workspace owner. Returns full Brand entity.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`brandId`	Yes	The unique identifier of the brand to retrieve.

Output Schema

TableJSON Schema

Name	Required	Description
`colors`	No	Color palette.
`brandId`	No	Brand ID.
`revision`	No	Current revision number.
`typography`	No	Typography settings.

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": "Brand ID.",
+      "type": "string"
+    },
+    "colors": {
+      "description": "Color palette.",
+      "type": "object"
+    },
+    "revision": {
+      "description": "Current revision number.",
+      "type": "number"
+    },
+    "typography": {
+      "description": "Typography settings.",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.1.16Oct 5, 2026
- addedInput schema / properties / brandId / description
```
Added value: +"The unique identifier of the brand to retrieve."
```
First observedv0.1.13Oct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds the workspace-owner scoping constraint and the workflow purpose (capture baseRevision before mutation), which is valuable beyond the annotations, though it doesn't discuss error cases for stale revision.

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-loads the fetch purpose and return contents, then adds the workflow hook and alternative. Slightly dense but every clause carries information; no filler.

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?

With an output schema present, return-value detail is not required, yet the description still summarizes key fields. Combined with annotations and the workflow guidance, an agent has everything needed to call this correctly.

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 coverage is 100% and the single brandId parameter is already documented. The description repeats 'by brandId' without adding format or sourcing detail beyond what list_brands provides. Baseline 3 applies when schema does the heavy lifting.

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+resource (fetch a Brand profile by brandId) and enumerates the returned contents (typography tokens, 4-color palette, logoAssetId, baseRevision). Clearly distinguished from siblings like list_brands and update_brand.

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?

Explicitly says to call it before generating or updating branded slides to inject brand styles and capture baseRevision, and names list_brands as the alternative for discovering brandIds. When-to-use is fully specified.

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