Skip to main content
Glama

linear_createReleasePipeline

Create a release pipeline for coordinating deployments. Specify teams, pipeline type, and optional production target or file path filters.

Instructions

Create a new release pipeline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the release pipeline
typeNoThe pipeline type
slugIdNoOptional unique slug identifier for the pipeline
teamIdsYesThe team identifiers associated with the pipeline
isProductionNoWhether the pipeline targets a production environment
includePathPatternsNoOptional glob patterns to limit matched commits by file path

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
nameNo
typeNo
teamsNo
slugIdNo
stagesNo
createdAtNo
updatedAtNo
archivedAtNo
productionNo
descriptionNo
pathPatternsNo
latestReleaseNoteNo
Behavior2/5

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

With all annotations set to false, the description carries full responsibility for behavioral disclosure. It does not mention any side effects, permissions required, or what happens upon creation. It adds no behavioral context beyond the basic action.

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

Conciseness3/5

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

The description is extremely concise (single sentence), but it sacrifices informativeness. It is not overly long, but it lacks structure and fails to convey important details expected for a creation tool.

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

Completeness2/5

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

Given the complexity of creating a release pipeline (6 parameters, output schema present), the description is far too minimal. It does not explain the return value, any constraints, or the relationship to other pipeline tools. This is incomplete for effective use.

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?

The input schema has 100% description coverage for all 6 parameters, so the schema already documents them. The description adds no additional meaning or context for any parameter, meeting the baseline for high coverage.

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 clearly identifies the verb ('Create') and the resource ('new release pipeline'), making the core action unambiguous. However, it lacks specificity to differentiate from sibling tools like 'createRelease' or 'createProject' that also use 'Create' as the verb.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., 'updateReleasePipeline' or 'archiveReleasePipeline'). There are no prerequisites, constraints, or use-case hints included.

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