Azure DevOps ACTION
List Work Item Revisions
List the revision history of a work item, one entry per change. Returns each revision's field values at that point in time. Use this to answer who changed what and when, or to reconstruct how long an item sat in a state. Example: work item
299. Returns at most Limit results per call - if that many come back there may be more, so raise Skip by Limit and call again to page through the rest. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Azure DevOps account once, then configure and run List Work Item Revisions 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-list-work-item-revisions",
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-list-work-item-revisions",
"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-list-work-item-revisions",
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 |
workItemId Work Item ID | integer | Numeric ID of the work item. Run the Query Work Items (WIQL) action first to obtain valid values. Required |
expand Expand | string | Additional work item attributes to include in each revision Optional |
limit Limit | integer | Maximum number of revisions to return (1-1000) Optional |
skip Skip | integer | Number of results to skip before returning matches. Use with Limit to page through results. 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-list-work-item-revisions
- Version
- 0.0.2
- App
- Azure DevOps
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗