Marketing Brain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_content_strategyA | Get the content strategy and template for a specific asset type. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusing it with another tool. The tool's purpose is clear and unambiguous.
With a single tool, naming consistency is trivially maintained. The name 'get_content_strategy' follows a clear verb_noun pattern.
The server is named 'Marketing Brain,' which implies a broad scope covering multiple marketing functions. Having only one tool is insufficient for this purpose, making the count too small.
A single 'get' operation is severely incomplete for a marketing strategy domain. Missing operations like create, update, delete, or analyze leave obvious gaps that agents cannot work around.