Azure DevOps ACTION
Query Analytics (OData)
Run an OData query against the Azure DevOps Analytics service, which holds the historical and aggregated data the work item APIs do not expose. Returns the matching rows plus the
@odata.context describing them. Use this for trend questions - how many bugs were open each day, how much work each iteration completed - and use Query Work Items (WIQL) instead for the current state of individual items. Set Apply to aggregate rather than pulling raw rows back. Example: entity set WorkItems, filter State eq 'Closed'. 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 Query Analytics (OData) 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-query-analytics",
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-query-analytics",
"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-query-analytics",
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 to scope the query to. Run the List Projects action first to obtain valid values. Omit to query across the whole organization. Optional |
entitySet Entity Set | string | Analytics entity set to query. Common values: WorkItems (current state of each item), WorkItemSnapshot (one row per item per day, the basis of burndown and trend charts), WorkItemRevisions, Iterations, Areas, Teams, PipelineRuns, TestRuns. Required |
filter Filter | string | OData $filter expression, e.g. StateCategory eq 'Completed' and WorkItemType eq 'Bug'. Escape a literal apostrophe by doubling it. Optional |
select Select | string | Comma-separated properties to return, e.g. WorkItemId,Title,State,StoryPoints. Narrow this - Analytics rows are wide. Optional |
orderby Order By | string | OData $orderby expression, e.g. ChangedDate desc Optional |
apply Apply | string | OData $apply aggregation, applied before the other options. Example: filter(StateCategory eq 'Completed')/groupby((Iteration/IterationName), aggregate(StoryPoints with sum as Points)). Supported aggregations are sum, average, min, max, countdistinct and $count. Optional |
expand Expand | string | Related entities to inline, e.g. Iteration,AssignedTo Optional |
limit Limit | integer | Maximum number of rows to return (1-1000) 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-query-analytics
- Version
- 0.0.2
- App
- Azure DevOps
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗