Skip to main content
Glama

get_brand_voice

Read-only

Get the active workspace's brand identity (positioning, audience/ICP, content pillars, current context) and the user's writing voice (how they sound, signature phrases, openers, what they avoid, recent feedback and edits). Call this BEFORE writing or editing any post copy yourself, so what you save with save_draft / update_draft sounds like the user and stays on-brand. draft_post already applies all of this server-side, so you don't need this tool first for that path, only when you are the one composing the words. To change what it returns, use update_voice (the user's own voice) or update_brand (the workspace's positioning and audience).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_brand_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoOptional: also return recent before/after edits captured for this platform
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description focuses on workflow behavior instead: it explains the server-side application inside draft_post and that save_draft/update_draft are the downstream consumers. It stops short of describing response shape or size, but the content enumeration partially covers that.

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?

Three tight sentences: what it returns, when to call it and the one exception, and where to change the data. The return-value list is dense but each item is meaningful; minor length cost from the parenthetical enumerations.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining what comes back, and it does so item by item. It also clarifies the relationship to draft_post and the two update tools, which is the main ambiguity for a read-only context tool.

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 both optional parameters (platform, workspace) are already fully documented in the schema, including the workspace/select_workspace distinction. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 ('Get the active workspace's brand identity ... and the user's writing voice') and enumerates the contents (positioning, ICP, pillars, signature phrases, openers, avoidances, recent feedback). It is clearly distinguishable from siblings like update_brand, update_voice, and draft_post, which it names directly.

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 an explicit trigger ('Call this BEFORE writing or editing any post copy yourself'), an explicit exclusion with the reason ('draft_post already applies all of this server-side, so you don't need this tool first for that path'), and routes mutation to update_voice/update_brand. No inference is required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources