Azure DevOps MCP Server

list_projects

Retrieve a list of all projects in an Azure DevOps organization, with options to filter by state, paginate using skip and top, or continue from a token.

Instructions

List all projects in an organization

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_projects"
  }
}

Input Schema

Name	Required	Description
`top`	No	Maximum number of projects to return
`skip`	No	Number of projects to skip
`stateFilter`	No	Filter on team project state (0: all, 1: well-formed, 2: creating, 3: deleting, 4: new)
`organizationId`	No	The ID or name of the organization (Default: mycompany)
`continuationToken`	No	Gets the projects after the continuation token provided

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 2, 2026

addedInput schema / properties / organizationId

Added value: +{
+  "description": "The ID or name of the organization (Default: mycompany)",
+  "type": "string"
+}

First observedApr 3, 2025

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral transparency. It only states 'list all projects' but fails to disclose pagination (via top, skip, continuationToken), ordering, authentication needs, or error scenarios. This is a significant gap for a list operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence, which is concise but lacks structure. It is front-loaded but too minimal to cover all necessary information. Every sentence should earn its place; this one is adequate but not optimized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters, no output schema, and no annotations, the description is incomplete. It omits key context like pagination, default filtering, and relationship to sibling tools (e.g., list_organizations). An agent would lack sufficient detail to use the tool effectively.

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?

Input schema coverage is 100%, with each parameter described. The description adds no additional meaning beyond the schema, achieving the baseline of 3. No extra value is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (list) and resource (projects in an organization), effectively distinguishing it from sibling tools like get_project or list_repositories. However, it could be more specific about pagination behavior to avoid ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like get_project (single project) or search tools. It lacks context for an agent to make an informed choice.

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

Deploy Server