Skip to main content
Glama
launchnotes

LaunchNotes MCP Server

Official
by launchnotes
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Remote

Create LaunchNotes Announcement

launchnotes_create_announcement

Create a draft announcement in a LaunchNotes project with a headline and optional content in Markdown, HTML, or Jira Wiki format.

Instructions

Create a new draft announcement in a LaunchNotes project. The announcement will be created in draft state.

Args:

  • project_id (string): The ID of the project

  • headline (string): The main headline/title (required)

  • content_markdown (string, optional): Content in Markdown format

  • content_html (string, optional): Content in HTML format

  • content_jira (string, optional): Content in Jira Wiki Syntax

Note: Provide only ONE content format. If multiple are provided, the API will use contentMarkdown > contentHtml > contentJira in order of precedence.

Returns: Created announcement with ID, headline, state, and creation timestamp

Use Cases:

  • "Create a new announcement about the API update"

  • "Draft an announcement for the new feature launch"

  • "Create announcement with headline 'v2.0 Released'"

Error Handling:

  • Returns validation errors if required fields are missing

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

  • Returns "Authentication failed" if API token lacks permission

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe ID of the LaunchNotes project
headlineYesThe main headline/title of the announcement
content_markdownNoThe full content/body of the announcement in Markdown format
content_htmlNoThe full content/body of the announcement in HTML format
content_jiraNoThe full content/body of the announcement in Jira Wiki Syntax

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Discloses draft state creation, content format precedence, and error responses. Annotations already indicate non-destructive mutation, but description adds useful behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections: purpose, args, note, returns, use cases, error handling. No extraneous information.

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?

Though no output schema, description specifies return fields (ID, headline, state, timestamp). Missing pagination or performance notes, but adequate for this 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?

Schema covers all parameters (100% coverage). Description adds important constraint: provide only ONE content format with explicit precedence order, which is beyond 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?

Clearly states 'Create a new draft announcement in a LaunchNotes project.' Specific verb+resource, and distinguishes from siblings like publish, archive, update, etc.

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

Usage Guidelines4/5

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

Provides use cases and error handling. Mentions content format precedence, but does not explicitly state when not to use this tool vs. alternatives like update_announcement.

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