SendIt

Create Brand Voice

create_brand_voice

Create a brand voice profile to guide AI content generation.

Configurable fields: • tone: Overall tone (professional, casual, energetic, witty, etc.) • personality: Brand personality description • writingStyle: Writing style guidelines • doRules: Array of things the brand voice SHOULD do • dontRules: Array of things the brand voice should NEVER do • examplePosts: Example posts in this brand voice • approvedHashtags: Preferred hashtags to prioritize • bannedWords: Words to never use in content • keyPhrases: Key phrases to incorporate naturally

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Name for this brand voice profile
`tone`	No	Overall tone (e.g., professional, casual, energetic)
`doRules`	No	Things the brand voice SHOULD do
`dontRules`	No	Things the brand voice should NEVER do
`isDefault`	No	Set as the default brand voice
`keyPhrases`	No	Key phrases to incorporate
`bannedWords`	No	Words to never use
`personality`	No	Brand personality description
`examplePosts`	No	Example posts in this voice
`writingStyle`	No	Writing style guidelines
`approvedHashtags`	No	Preferred hashtags

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedMay 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds no behavioral detail beyond the action itself, such as side effects, permissions, or overwrite behavior. It does not contradict the annotations, so a baseline score of 3 is appropriate.

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?

The description is well-structured with a clear opening sentence followed by a bulleted list of configurable fields. It is somewhat long due to 11 fields, but each bullet is concise and earns its place. The front-loading of purpose is effective.

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?

Given the tool's complexity (11 parameters) and full schema coverage, the description covers all parameters and the overall purpose. It lacks details about the response format or side effects, but since there is no output schema, this is a minor gap. The description is otherwise comprehensive for invoking the tool 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 description coverage is 100%, and the description lists all fields with brief clarifications (e.g., 'approvedHashtags: Preferred hashtags to prioritize'). While this adds slight detail over the schema, it largely repeats what the schema already provides, yielding a baseline score of 3.

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?

The description clearly states the tool's action ('Create a brand voice profile') and its purpose ('to guide AI content generation'). It distinguishes itself from sibling tools like list_brand_voices and set_default_brand_voice by focusing on the creation action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context that this tool is for creating a brand voice profile to guide AI content generation, implying when it would be used. However, it does not explicitly mention alternatives, prerequisites, or when not to use it, unlike a fully guided description.

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

All SendIt tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0

Disambiguation2/5

With 148 tools, there is significant overlap. For example, generate_content, publish_ai, generate_post_bundle, and request_project_content all generate content; get_analytics, get_unified_analytics, get_post_analytics, get_ad_performance, and get_unified_ad_report all fetch performance metrics; and list_inbox vs list_conversations blur comment and conversation management. Descriptions help, but boundaries between tools are often unclear.

Naming Consistency3/5

Most tools follow a verb_noun pattern (e.g., list_teams, create_goal, delete_post), but there are notable deviations: create_library_item vs save_to_library, publish_content vs publish_ai, schedule_content vs schedule_content_advanced, and connect_platform vs connect_connector. Mixed prefixes like 'autopilot_', 'check_', and 'get_' are fine, but overlapping verbs and a hyphen in 'connect_linkedin-page' reduce consistency.

Tool Count1/5

148 tools is extreme for any server. Even for a broad social media management platform, this is far beyond what an agent can effectively navigate. The count is unwieldy and suggests the surface should be split into multiple focused servers (publishing, analytics, connectors, workflows, etc.).

Completeness3/5

The core social publishing workflow is well covered (create, schedule, publish, edit, delete, retry), and there are extensive features for analytics, workflows, connectors, and AI agents. However, some resources have CRUD gaps: no update/delete for brand voices, no delete_project, no update/delete for Product Hunt goals, and no explicit get_workflow. These are workable but notable omissions.

Resources

Need Help?