Azure DevOps MCP Server

get_release_logs

Retrieve deployment logs for a release environment by specifying the release and environment IDs.

Instructions

Get deployment logs for a release environment

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "releaseId": "<releaseId>",
      "environmentId": "<environmentId>"
    },
    "name": "get_release_logs"
  }
}

Input Schema

Name	Required	Description
`project`	No	Project name
`releaseId`	Yes	Release ID
`environmentId`	Yes	Environment ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Jun 3, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states 'Get' implying a read-only operation, but does not explicitly mention safety, permissions, rate limits, or return format. 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.

Conciseness5/5

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

The description is a single, focused sentence with no filler. It front-loads the verb and resource, making it immediately scannable.

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?

The tool is a simple get operation with well-documented parameters, but without annotations or an output schema, the description leaves gaps about what 'logs' entails and any response shape. It is minimally adequate but lacks helpful context for correct 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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for releaseId and environmentId. It names the resource but does not elaborate on parameter relationships or expected values.

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 uses a specific verb ('Get') and resource ('deployment logs for a release environment'), clearly distinguishing it from siblings like get_build_logs or get_release. It immediately conveys what the tool returns.

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 implies usage for retrieving deployment logs tied to a release environment, but provides no explicit guidance on when to choose this tool over alternatives like get_build_logs or get_pipeline_runs. No exclusions or alternative tool references are given.

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