Brand and context

Find an existing brand

1. Use api_listBrandKits in the selected teamspace.
2. Match the requested brand to its ID.
3. Read the complete kit with api_getBrandKit.
4. Inspect related context with api_listContextDocuments and api_getContextDocument.

Read the Acme brand kit and its audience and voice context. Summarize the rules you will use before drafting our launch posts.

Use api_getContextDocumentByType when you know the context type. Discover supported types from the tool schema rather than inventing one.

Build a brand kit

Use api_buildBrandKit to build brand information from a website when that is the desired workflow. Review the extracted result before treating it as authoritative: a website may contain outdated copy or multiple product brands.

Use api_createBrandKit when you already have the required brand information and want to supply it directly. Check the existing kits first to avoid creating a duplicate.

Maintain supporting context

Create a context document with api_createContextDocument for information such as audience guidance, positioning, or campaign instructions, using the supported document types and fields. Read the current version before applying api_updateContextDocument.

Update the audience context to include independent consultants. Preserve the existing small-business segment and show me the revised document.

Delete a context document only when you intend to remove it. A request to revise wording should update the existing document instead.

Apply the brand to a deliverable

The assistant must read and use the kit; simply connecting MCP does not apply a brand to every operation automatically. Include relevant voice and visual constraints in generation prompts and check the output against them.

Continue with AI generation or social publishing.