TeamCity MCP Server

get_build_status

Read-onlyIdempotent

Retrieve build status with optional test summaries, problem details, and queue context to monitor CI/CD pipeline health.

Instructions

Get build status. Optionally includes test and problem summaries plus queue context.

Input Schema

TableJSON Schema

Name	Required	Description
`buildId`	No	Build ID
`buildNumber`	No	Human build number (requires buildTypeId when provided)
`buildTypeId`	No	Build configuration identifier (required when using buildNumber)
`includeTests`	No	Include test summary
`includeProblems`	No	Include build problems
`includeQueueReason`	No	Include waitReason for the queued item (extra API call when queued)
`includeQueueTotals`	No	Include total queued count (extra API call when queued)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`state`	Yes
`status`	No
`webUrl`	No
`buildId`	Yes
`problems`	No
`startDate`	No
`branchName`	No
`canceledBy`	No
`finishDate`	No
`queuedDate`	No
`statusText`	No
`waitReason`	No
`buildNumber`	No
`buildTypeId`	No
`testSummary`	No
`totalQueued`	No
`canMoveToTop`	No
`canceledDate`	No
`failureReason`	No
`queuePosition`	No
`elapsedSeconds`	No
`currentStageText`	No
`estimatedStartTime`	No
`percentageComplete`	Yes
`estimatedTotalSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.2May 12, 2026
Removedv1.0.1May 10, 2026

Changed3 schema fields changedv1.0.0Jan 3, 2026

addedInput schema / properties / buildNumber

Added value: +{
+  "description": "Human build number (requires buildTypeId when provided)",
+  "type": "string"
+}

addedInput schema / properties / buildTypeId

Added value: +{
+  "description": "Build configuration identifier (required when using buildNumber)",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "buildId"
-]
```

First observedSep 20, 2025

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already provide readOnlyHint and idempotentHint, so the description adds minimal behavioral info. It mentions optional summaries and queue context, which is consistent 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.

Conciseness4/5

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

Single sentence, no fluff, but could be expanded slightly to improve clarity without adding verbosity.

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

Completeness3/5

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

With rich schema and output schema, the description suffices for the core function. However, it lacks usage differentiation from sibling tools, which is a gap in context.

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 100% with detailed parameter descriptions. The description adds value by grouping boolean flags into 'test and problem summaries plus queue context', providing a higher-level understanding.

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 states 'Get build status' as the main action, and mentions optional summaries and queue context. However, it does not distinguish this tool from sibling 'get_build', which may cause confusion.

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 on when to use this tool versus alternatives like 'get_build' or 'get_build_results'. The agent is left to guess based on name alone.

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