Skip to main content
Glama

Create Release

create_release

Create a new release in TestDino with project, schedule, build target, testers, and optional parent release for nesting.

Instructions

Create a new release. Requires write permission. Use parentReleaseId to nest under another release (max 3 levels deep). startDate/endDate are ISO date strings. isStarted/isCompleted are independent flags — startedAt/completedAt are recorded separately. branch/environment/buildTarget/testers describe what build the release ships and who tests it (testers must be org members — pass User _ids).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "name": "<name>"
    },
    "name": "create_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRelease name
noteNoRich HTML note
typeNoRelease type. Default options: "release", "version", "sprint", "iteration", "plan", "cycle", "feature" (case-insensitive — server lowercases on save so the UI badge color matches). Projects can add or rename types via Project Settings → Release Types; pass the value the project actually has.
branchNoSource branch this release ships from.
endDateNoISO date
testersNoUser _ids assigned as testers. Must be members of the org.
isStartedNo
projectIdYesProject ID
startDateNoISO date
startedAtNoISO datetime
buildTargetNoBuild the release cuts against: { platform: "web"|"ios"|"android"|"api", version, buildNumber, source, deployUrl }. An all-empty object is stored as null.
completedAtNoISO datetime
descriptionNo
environmentNoEnvironment label this release targets, e.g. "Staging".
isCompletedNo
linkedIssuesNoArray of linked-issue objects (same shape as list_releases returns).
parentReleaseIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / branch / description
      Previous value: -"Source branch this release ships from"New value: +"Source branch this release ships from."
    • addedInput schema / properties / buildTarget / additionalProperties
      Added value: +true
    • changedInput schema / properties / buildTarget / description
      Previous value: -"Build target details."New value: +"Build the release cuts against: { platform: \"web\"|\"ios\"|\"android\"|\"api\", version, buildNumber, source, deployUrl }. An all-empty object is stored as null."
    • removedInput schema / properties / buildTarget / properties / buildNumber / description
      Removed value: -"Build number."
    • removedInput schema / properties / buildTarget / properties / deployUrl / description
      Removed value: -"Deployment URL."
    • addedInput schema / properties / buildTarget / properties / platform / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "web",
      +      "ios",
      +      "android",
      +      "api"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / buildTarget / properties / platform / description
      Removed value: -"Build platform."
    • removedInput schema / properties / buildTarget / properties / platform / enum
      Removed value: -[
      -  "web",
      -  "ios",
      -  "android",
      -  "api"
      -]
    • removedInput schema / properties / buildTarget / properties / platform / type
      Removed value: -"string"
    • removedInput schema / properties / buildTarget / properties / source / description
      Removed value: -"Build source."
    • removedInput schema / properties / buildTarget / properties / version / description
      Removed value: -"Build version."
    • changedInput schema / properties / completedAt / description
      Previous value: -"ISO datetime."New value: +"ISO datetime"
    • changedInput schema / properties / endDate / description
      Previous value: -"ISO date."New value: +"ISO date"
    • changedInput schema / properties / environment / description
      Previous value: -"Environment label, e.g. 'Staging'"New value: +"Environment label this release targets, e.g. \"Staging\"."
    • changedInput schema / properties / linkedIssues / description
      Previous value: -"Array of linked-issue objects (same shape list_releases returns)."New value: +"Array of linked-issue objects (same shape as list_releases returns)."
    • addedInput schema / properties / linkedIssues / items / additionalProperties
      Added value: +true
    • addedInput schema / properties / linkedIssues / items / properties
      Added value: +{
      +  "displayId": {
      +    "type": "string"
      +  },
      +  "issueType": {
      +    "type": "string"
      +  },
      +  "source": {
      +    "type": "string"
      +  },
      +  "status": {
      +    "type": "string"
      +  },
      +  "title": {
      +    "type": "string"
      +  },
      +  "url": {
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / linkedIssues / items / type
      Added value: +"object"
    • changedInput schema / properties / name / description
      Previous value: -"Release name (required)."New value: +"Release name"
    • changedInput schema / properties / note / description
      Previous value: -"Rich HTML note."New value: +"Rich HTML note"
    • removedInput schema / properties / parentReleaseId / description
      Removed value: -"Parent release for nesting."
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / startDate / description
      Previous value: -"ISO date."New value: +"ISO date"
    • changedInput schema / properties / startedAt / description
      Previous value: -"ISO datetime."New value: +"ISO datetime"
    • changedInput schema / properties / testers / description
      Previous value: -"User _ids assigned as testers; must be org members"New value: +"User _ids assigned as testers. Must be members of the org."
    • changedInput schema / properties / type / description
      Previous value: -"Release type. Either canonical ('iteration', 'major') or display ('Iteration', 'Major') form — server normalizes to lowercase so UI badge color matches."New value: +"Release type. Default options: \"release\", \"version\", \"sprint\", \"iteration\", \"plan\", \"cycle\", \"feature\" (case-insensitive — server lowercases on save so the UI badge color matches). Projects can add or rename types via Project Settings → Release Types; pass the value the project actually has."
  2. Changed4 schema fields changedv2.0.2
    • addedInput schema / properties / branch
      Added value: +{
      +  "description": "Source branch this release ships from",
      +  "type": "string"
      +}
    • addedInput schema / properties / buildTarget
      Added value: +{
      +  "description": "Build target details.",
      +  "properties": {
      +    "buildNumber": {
      +      "description": "Build number.",
      +      "type": "string"
      +    },
      +    "deployUrl": {
      +      "description": "Deployment URL.",
      +      "type": "string"
      +    },
      +    "platform": {
      +      "description": "Build platform.",
      +      "enum": [
      +        "web",
      +        "ios",
      +        "android",
      +        "api"
      +      ],
      +      "type": "string"
      +    },
      +    "source": {
      +      "description": "Build source.",
      +      "type": "string"
      +    },
      +    "version": {
      +      "description": "Build version.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / environment
      Added value: +{
      +  "description": "Environment label, e.g. 'Staging'",
      +  "type": "string"
      +}
    • addedInput schema / properties / testers
      Added value: +{
      +  "description": "User _ids assigned as testers; must be org members",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Addedv1.0.10

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare write semantics (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds genuinely new context: the write-permission requirement, a hard nesting-depth limit of 3, and the non-obvious rule that isStarted/isCompleted are independent of startedAt/completedAt. It still omits what happens on failure (e.g. duplicate names) or whether partial input is silently dropped.

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?

Six short sentences with the core action and permission prerequisite front-loaded, then parameter guidance in the order an agent would need it. A few clauses restate schema facts (ISO dates, org-member testers), which is minor redundancy rather than padding.

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?

For a 17-parameter mutation with nested objects and no output schema, the description covers permissions, nesting limits, and the trickiest flag semantics, and the schema covers the rest. Return behavior is left unstated but there is no output schema to explain, so the remaining gap is small.

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 a high 76%, so the schema carries most parameter documentation, and the description still adds meaning: the 3-level cap on parentReleaseId, the flag-versus-timestamp independence for start/complete, and that testers must be org member User _ids. It repeats 'ISO date strings' for startDate/endDate, which the schema already states, and leaves note, linkedIssues, and type to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 pair ('Create a new release'), matching the name and title, and the body makes clear it is the creation entry point for releases. It does not explicitly name update_release or get_release as the alternatives, so an agent must infer the boundary from the verb alone.

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?

It states a concrete prerequisite ('Requires write permission') and a conditional usage rule for nested releases ('Use parentReleaseId to nest under another release (max 3 levels deep)'). It gives no exclusion guidance, e.g. when to prefer update_release over creating a new record, which keeps it below a 5.

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