Skip to main content
Glama
Sign In
Azure DevOps MCP Server

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

manage_work_item_link

Add, remove, or update links between work items in Azure DevOps to define relationships such as parent-child or related items.

Instructions

Add or remove links between work items

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sourceWorkItemId": "<sourceWorkItemId>",
      "targetWorkItemId": "<targetWorkItemId>",
      "operation": "<operation>",
      "relationType": "<relationType>"
    },
    "name": "manage_work_item_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional comment explaining the link
operationYesThe operation to perform on the link
projectIdNoThe ID or name of the project (Default: MyProject)
relationTypeYesThe reference name of the relation type (e.g., "System.LinkTypes.Hierarchy-Forward")
organizationIdNoThe ID or name of the organization (Default: mycompany)
newRelationTypeNoThe new relation type to use when updating a link
sourceWorkItemIdYesThe ID of the source work item
targetWorkItemIdYesThe ID of the target work item

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / organizationId
      Added value: +{
+  "description": "The ID or name of the organization (Default: mycompany)",
+  "type": "string"
+}
    • changedInput schema / properties / projectId / description
      Previous value: -"The ID or name of the project"New value: +"The ID or name of the project (Default: MyProject)"
    • changedInput schema / required
      Previous value: -[
-  "sourceWorkItemId",
-  "targetWorkItemId",
-  "projectId",
-  "operation",
-  "relationType"
-]New value: +[
+  "sourceWorkItemId",
+  "targetWorkItemId",
+  "operation",
+  "relationType"
+]
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure, but it only states the basic function. It does not mention side effects, permission requirements, or what happens when links already exist, leaving significant gaps.

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 concise sentence, but it lacks structure and fails to convey important details. It is not overly verbose, but it could be more informative without losing conciseness.

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's complexity (8 parameters, multiple operations, no output schema), the description is insufficient. It does not explain the nature of links, relation types, or return values, leaving the agent underinformed for correct invocation.

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?

The input schema provides full description coverage (100%), so the tool description does not need to elaborate on parameters. It adds no additional meaning beyond the schema, meeting the baseline of 3.

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 tool adds or removes links between work items, which aligns with its name and distinguishes it from sibling tools that handle work items directly. However, it omits the 'update' operation that is available in the schema, creating a minor inconsistency.

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?

No guidance is provided on when to use this tool versus alternatives like update_work_item or other link-related operations. The description does not mention prerequisites, context, or when not to use it.

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

Deploy Server

Other Tools