Azure DevOps ACTION
Create Pull Request Comment
Start a new comment thread on a pull request, either on the overview or anchored to a line in a file. Returns the new thread with its id. Use this to post automated review findings where the reviewer will see them. Example: pull request
12, file /src/index.js line 42, comment This drops the null check. See the documentation- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Azure DevOps account once, then configure and run Create Pull Request Comment from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "azure_devops-create-pull-request-comment",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
azure_devops: { authProvisionId: "apn_xxxxxxx" },
organization: "Organization",
project: "Project",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "azure_devops-create-pull-request-comment",
"configured_props": {
"azure_devops": { "authProvisionId": "apn_xxxxxxx" },
"organization": "Organization",
"project": "Project"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "azure_devops",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "azure_devops-create-pull-request-comment",
arguments: {
organization: "Organization",
project: "Project",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
organization Organization | string | Name of the organization Required Dynamic |
project Project | string | Project ID or project name. Run the List Projects action first to obtain valid values. Required |
repositoryId Repository | string | Repository ID or repository name. Run the List Repositories action first to obtain valid values. Required |
pullRequestId Pull Request ID | integer | Numeric ID of the pull request. Run the List Pull Requests action first to obtain valid values. Required |
content Comment | string | Text of the comment. Markdown is supported. Required |
status Thread Status | string | Status to open the thread in. Defaults to active. Optional |
filePath File Path | string | Repository-relative path of the file to anchor the thread to, e.g. /src/index.js. Omit to comment on the pull request overview. Optional |
rightFileLine Line Number | integer | Line in the file's right-hand (new) side to anchor the thread to. Requires File Path. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- azure_devops-create-pull-request-comment
- Version
- 0.0.2
- App
- Azure DevOps
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗