get_pull_request_thread_commentsRetrieve all comments within a specific pull request thread by providing repository, pull request, and thread IDs.
List comments inside one pull request thread.
| Name | Required | Description | Default |
|---|---|---|---|
| project | No | Project name or ID. Omit to use AZURE_DEVOPS_DEFAULT_PROJECT. | |
| threadId | Yes | ||
| repositoryId | Yes | Repository name or ID. | |
| pullRequestId | Yes | Pull request numeric ID. |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. 'List comments' conveys a non-mutating read operation, but it does not mention ordering, pagination, whether system comments are included, or authorization requirements. It is adequate for a simple read, but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no redundant words. Every part earns its place, and the key information appears immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a simple read operation with four parameters already documented in the schema. However, with no output schema and no annotation context, the description does not explain what the returned comments look like, how they are ordered, or how errors are surfaced. It is minimally sufficient but leaves some invocation-relevant details implicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 75%, so the schema already documents most parameters. The description does not add meaning beyond the schema; it only restates the concept of a thread. The baseline of 3 applies because the schema already carries the parameter documentation load.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('List'), a specific resource ('comments'), and a precise scope ('inside one pull request thread'), which clearly distinguishes it from sibling tools like get_pull_request_threads or create_pull_request_comment. The tool name and title reinforce but do not replace the description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'one pull request thread' implies the context: use this when you already have a threadId and need its comments. However, the description does not explicitly say when to prefer this over sibling tools such as get_pull_request_threads or comment-creation tools, nor does it state that it is read-only or give exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.