Skip to main content
Glama
launchnotes

LaunchNotes MCP Server

Official
by launchnotes

Update LaunchNotes Project Colors

launchnotes_update_project_colors

Update a LaunchNotes project's color palette and theme using hex color values for primary, secondary, text, and accent colors. Modify brand colors or switch to a dark theme.

Instructions

Update color palette and theme for a LaunchNotes project. All colors must be in hex format (e.g., #FF5733).

Args:

  • project_id (string): The ID of the project to update

  • primary_color (string, optional): Primary brand color (hex)

  • secondary_color (string, optional): Secondary brand color (hex)

  • primary_text_color (string, optional): Primary text color (hex)

  • secondary_text_color (string, optional): Secondary text color (hex)

  • gray_color (string, optional): Gray accent color (hex)

  • light_gray_color (string, optional): Light gray color (hex)

  • off_white_color (string, optional): Off-white color (hex)

  • white_color (string, optional): White color (hex)

  • supporting_palette (string, optional): Supporting palette configuration

  • color_theme (string, optional): Overall color theme identifier

At least one color field must be provided. Fields not provided will remain unchanged.

Returns: Confirmation message with updated color fields

Use Cases:

  • "Change the primary color to #FF5733"

  • "Update all brand colors for my project"

  • "Set text colors to improve readability"

  • "Update the color theme to dark mode"

Error Handling:

  • Returns validation error if hex colors are invalid

  • Returns "Project not found" if the project ID doesn't exist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations indicate mutable, non-destructive, non-idempotent, and partial updates. The description adds context by stating unprovided fields remain unchanged and details error handling for invalid hex and missing project ID.

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 structured into sections (general description, Args, returns, use cases, error handling) and is front-loaded with the purpose. Could be slightly more concise but well-organized.

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 many optional parameters and no output schema, the description covers required inputs, behavior (unchanged fields), error cases, and includes examples. Reasonably complete for a configuration update tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty, so the description carries full burden. It lists all 11 parameters with types, optionality, and format requirements (hex), adding significant value beyond the schema.

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 'Update color palette and theme for a LaunchNotes project' with specific verb and resource. Use cases reinforce the purpose and differentiate from siblings like update_project_content.

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 some usage context through use cases and notes that at least one color field must be provided, but it does not explicitly state when to use this tool versus alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/launchnotes/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server