Skip to main content
Glama
m00nreport

M00N Report MCP

Official
by m00nreport
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

create_release

Create a new release in a project to track versions and aggregate test results. Provide projectId and release name; optionally set status, dates, and version.

Instructions

Create a new release in a project. Releases track versions and aggregate manual and automated test results. projectId comes from list_projects. Omit status to default to "planned". Returns the created release with id, name, version, description, status, startDate, endDate, projectId, projectName, createdAt and updatedAt; keep the id, it is what the other release tools take. Not idempotent - calling twice with the same name creates two separate releases, so check list_releases first. When the release already exists and only its name, version, dates or status should change, use update_release instead. The new release starts empty and nothing else is modified: attach automated launches with link_launches_to_release, and attach manual executions from the execution side via the releaseIds argument of create_execution or update_execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRelease name (e.g., "Sprint 42", "v2.1.0 Release")
statusNoOptional. Release status from the project vocabulary, typically planned, in_progress, completed or cancelled, plus any the project added; call get_project for the list. Omit to use whichever value the project marks as its default.
endDateNoTarget end/release date (YYYY-MM-DD)
versionNoVersion string (e.g., "2.1.0", "2026-Q1")
projectIdYesProject UUID to create release in
startDateNoRelease start date (YYYY-MM-DD)
descriptionNoDetailed description of the release scope

Schema Changelog

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

  1. Changed3 schema fields changedv1.5.3
    • removedInput schema / properties / status / default
      Removed value: -"planned"
    • changedInput schema / properties / status / description
      Previous value: -"OPTIONAL - defaults to \"planned\". Valid: planned, in_progress, completed, cancelled."New value: +"Optional. Release status from the project vocabulary, typically planned, in_progress, completed or cancelled, plus any the project added; call get_project for the list. Omit to use whichever value the project marks as its default."
    • removedInput schema / properties / status / enum
      Removed value: -[
-  "planned",
-  "in_progress",
-  "completed",
-  "cancelled"
-]
  2. First observedv1.5.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already signal a read/write safety profile, and the description meaningfully extends this by declaring the call is not idempotent, that duplicate names create separate releases, and that the new release starts empty without modifying anything else. It also states what is returned, including the fields and why keeping the id matters.

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?

The description is dense but every sentence earns its place: the main purpose comes first, then defaults, duplicate behavior, alternatives, and downstream workflow. It gives a lot of needed context without repeating schema content or adding filler.

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

Completeness5/5

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

Given 7 parameters, no output schema, and no enums, the description closes the important gaps itself: return shape, id retention for sibling tools, duplicate pitfalls, property updates route, and the relationship to related execution and launch tools. The only omissions, such as error conditions, are not critical enough to hurt an agent correctly invoking 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 coverage is 100%, so the structured field descriptions already explain each parameter. The description adds useful extra meaning, such as sourcing projectId from list_projects, the status default behavior, and where to resolve project-specific release statuses via get_project. This is a strong complement to the schema, though some parameters still rely mostly on their own schema descriptions.

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 states a specific action ('Create a new release in a project') on a specific resource and explains what releases are for. It clearly differentiates this tool from update_release and delete_release, which is enough for an agent to select it correctly.

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?

The description gives concrete before-you-call guidance: get projectId from list_projects, check list_releases first because the call is not idempotent, and use update_release when only modifying an existing release. It also explains how manual executions should be linked on the execution side, so the tool is placed in the correct workflow.

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/m00nreport/mcp-server'

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