Skip to main content
Glama

linear_createReleaseNote

Create a release note for a pipeline by specifying explicit release IDs or a date range to generate a changelog.

Instructions

Create a release note using either explicit release IDs or a release range within a pipeline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNoOptional release note content in markdown
pipelineIdYesThe ID of the release pipeline that owns the release note
releaseIdsNoExplicit release IDs to include in the note
rangeToReleaseIdNoNewest release ID in the release note range
rangeFromReleaseIdNoOldest release ID in the release note range

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
titleNo
slugIdNo
contentNo
releasesNo
createdAtNo
updatedAtNo
lastReleaseNo
Behavior3/5

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

Annotations fully cover the non-readonly nature; description adds the two creation modes but lacks further behavioral context like permissions or side effects. No contradictions with annotations.

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?

Single sentence, no wasted words, front-loaded with purpose. Every word earns its place.

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 two modes and mentions pipeline ownership. With output schema present (inferred), it provides sufficient context for a tool of moderate complexity.

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?

All 5 parameters have detailed schema descriptions (100% coverage), so the description adds only marginal value by summarizing the two modes. 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 clearly states the action (create), the object (release note), and the two methods (explicit IDs or range), distinguishing it from related tools like linear_getReleaseNotes and linear_updateReleaseNote.

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 explains the two usage modes (explicit IDs vs range) but does not explicitly state when not to use this tool or mention alternatives like linear_updateReleaseNote for editing existing notes.

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/tacticlaunch/mcp-linear'

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