Call the getBrandProfile MCP tool

Read the workspace's brand profile. Without arguments: the compact summary (company name, industry, target audience, tone, selling features, mission, promise, products, beliefs, pillars, objection/case-study counts, has_knowledge, sections_filled). With sections ("all" or a list of section names): the FULL contents of each section plus the sources ledger, which is what to read before researching, editing, or replacing anything. Call before writing campaign or post copy. If it returns exists:false and your key has the write scope, research the company and propose a profile with updateBrandProfile (see getPlaybook("copywriting", "brand-profile-research")); on a read-only key, ask the user to fill in their brand profile in the Reachium app.

Called through the Actions bridge: the response is that tool's own result, wrapped as { data: <tool result> } under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE data, never remapped to an HTTP status (see the templated /api/v1/actions/{toolName} operation above for the full protocol, and x-mcp-actions for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.