Skip to main content
Glama
Sign In
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Create Release

create_release

Create a product release by specifying a version and optional changelog and release date. Returns release details; omit the date to save a draft.

Instructions

Create a release and return it (id, version, changelog, released_at). Omit released_at for an unreleased/draft entry. product_id defaults to the org's primary product. Only version is required.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "version": "v2.4.0",
      "changelog": "SSO + faster board",
      "released_at": "2026-07-15T00:00:00Z"
    },
    "name": "create_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesVersion string (required), e.g. 'v2.4.0'.
changelogNoWhat shipped (optional).
product_idNoProduct, from whoami (optional; the primary product when omitted).
released_atNoShip time, ISO 8601 (optional; omit for a draft).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.14
  2. Removedv0.1.12
  3. Addedv0.1.6

TDQS

A4.2/5.0
Behavior4/5

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

Given that annotations are all false (no hints), the description carries the burden of disclosure. It clearly states what is returned, the optionality of released_at, and the default for product_id. This adds meaningful behavioral context beyond the schema and annotations, though it does not mention side effects like potential validation errors.

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 three sentences, front-loaded with the primary action, and every sentence adds valuable information. No filler or redundancy.

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?

The description covers the return format, draft behavior, default behavior, and required parameter. With no output schema, this is sufficient for an agent to invoke the tool correctly and understand the basic result. It lacks error-condition details, but they are not critical for a simple create operation.

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%, so the schema already explains each parameter. The description reiterates the semantics of released_at and product_id but does not add new information beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb+resource ('Create a release') and explicitly states return fields and the only required parameter. This clearly distinguishes it from sibling tools like update_release or list_releases.

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?

The description provides clear context on usage, including draft behavior ('Omit released_at for a draft') and defaulting behavior for product_id. It does not explicitly name alternatives or exclusions, but the context is sufficient for selecting this tool for creating a release.

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

Deploy Server

Other Tools