Skip to main content
Glama
nikydobrev

Azure DevOps Multi-Organization MCP Server

by nikydobrev

pipelines_get_build_log

Retrieve build log files from Azure DevOps to analyze pipeline execution details and troubleshoot issues.

Instructions

Gets the list of log files for a build

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesThe name of the Azure DevOps organization
projectYesProject ID or name to get the build log for
buildIdYesID of the build to get the log for

Implementation Reference

  • The handler function that fetches the list of build logs for the specified build using the Azure DevOps Build API and returns them as a JSON string in the tool response.
    async ({ organization, project, buildId }) => {
        const connection = await connectionManager.getConnection(organization);
        const buildApi = await connection.getBuildApi();
        const logs = await buildApi.getBuildLogs(project, buildId);
        return {
            content: [{ type: "text", text: JSON.stringify(logs, null, 2) }],
        };
    }
  • Zod schema defining the input parameters for the tool: organization (string), project (string), buildId (number).
    {
        organization: z.string().describe("The name of the Azure DevOps organization"),
        project: z.string().describe("Project ID or name to get the build log for"),
        buildId: z.number().describe("ID of the build to get the log for"),
    },
  • Registration of the 'pipelines_get_build_log' tool on the MCP server, including name, description, input schema, and handler function.
    server.tool(
      "pipelines_get_build_log",
      "Gets the list of log files for a build",
      {
          organization: z.string().describe("The name of the Azure DevOps organization"),
          project: z.string().describe("Project ID or name to get the build log for"),
          buildId: z.number().describe("ID of the build to get the log for"),
      },
      async ({ organization, project, buildId }) => {
          const connection = await connectionManager.getConnection(organization);
          const buildApi = await connection.getBuildApi();
          const logs = await buildApi.getBuildLogs(project, buildId);
          return {
              content: [{ type: "text", text: JSON.stringify(logs, null, 2) }],
          };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Gets') but doesn't cover critical aspects like authentication needs, rate limits, pagination, error handling, or the format of returned log files. This leaves significant gaps for an agent to understand how to use it effectively.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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 a build log tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'log files' entail, how they are structured, or any behavioral traits, leaving the agent with incomplete context for proper invocation.

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?

Schema description coverage is 100%, so the input schema fully documents the three parameters (organization, project, buildId). The description adds no additional meaning beyond implying a relationship to 'build' and 'log files', which is already inferred from the schema. This meets the baseline for high schema 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 states the verb ('Gets') and resource ('list of log files for a build'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'pipelines_get_build_log_by_id' or explain what distinguishes 'log files' from other build data, missing full sibling differentiation.

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 such as 'pipelines_get_build_log_by_id' or other build-related tools. The description lacks context about prerequisites, timing, or exclusions, offering minimal usage direction.

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/nikydobrev/mcp-server-azure-devops-multi'

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