Skip to main content
Glama
Inflectra

Inflectra Spira MCP Server

Official
by Inflectra

product_create_build

Creates a new CI/CD pipeline build entry in Spira, recording build results and associating commits with a specific release.

Instructions

    Creates a new CI/CD pipeline build entry in Spira.

    Maps to Spira API: POST /projects/{product_id}/releases/{release_id}/builds

    Use this to record CI/CD build results and associate commits with releases.

    Args:
        product_id: The numeric ID of the product (e.g., 55 for PR:55). If omitted, uses SPIRA_PROJECT_ID from environment.
        release_id: Release/sprint ID without RL prefix (e.g., 12 for RL:12)
        build_status_id: Build status (1=Failed, 2=Passed)
        name: Build name (typically project name + date/time)
        description: Detailed build description (what was included and why)
        commits: Array of Git commit hashes included in the build

    Returns:
        JSON: {"build_id": "BL:123", "message": "Build created successfully"}

    Error Responses:
        Returns structured JSON with error, error_code, details, and suggestion.
        Common error codes: INVALID_PARAMETER, API_ERROR, NOT_FOUND

    Example Usage:
        result = create_build(
            product_id=55, release_id=10, build_status_id=2,
            name="Build 2024-02-13 v1.5.0", description="Production build",
            commits=["abc123", "def456"]
        )
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
release_idYes
build_status_idYes
nameYes
descriptionYes
commitsYes
product_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate readOnlyHint=false, and the description confirms creation. It discloses return format and error responses, adding value beyond annotations. However, it does not mention side effects like notifications or permission requirements.

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?

The description is well-structured with sections (purpose, mapping, args, returns, errors, example), but includes slightly redundant information (e.g., API endpoint). Front-loaded with purpose.

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?

Given 6 parameters (5 required) and no schema descriptions, the description covers inputs, output format, errors, and provides an example. It lacks details on rate limits or authentication, but is largely complete for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter, including default behavior for product_id, value mapping for build_status_id, and expected format for commits. Example usage further clarifies.

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 it creates a new CI/CD pipeline build entry in Spira, with a direct API mapping. It distinguishes itself from sibling tools like product_create_automated_test_run by focusing on builds.

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 specifies when to use it ('record CI/CD build results and associate commits with releases'), providing clear context. However, it does not explicitly exclude alternative tools or scenarios.

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

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