Skip to main content
Glama

Add Kanban Item

add_kanban_item
Idempotent

Adds an existing GitHub Issue or Pull Request to a GitHub Project v2 Kanban board, returning the project item ID so the work item can be tracked.

Instructions

Add an existing GitHub Issue or Pull Request to a Kanban board (GitHub Project v2). Returns the project item ID on success.

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": "add_kanban_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name - LEAVE EMPTY to auto-detect
ownerNoRepository owner - LEAVE EMPTY to auto-detect
use_test_dbNo
issue_numberNoThe number of the issue or PR to add
project_numberNoGitHub Project number (optional if repo is registered)

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
itemIdNo
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
projectNumberNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.1.0
    • changedInput schema / properties / issue_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
    • changedInput schema / properties / project_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only the success return value (project item ID) and the v2 backend; it says nothing about what happens when the issue is already on the board, or about authentication/permission requirements.

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

Conciseness5/5

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

Two short sentences, the core action front-loaded, and the return value stated at the end. No filler or repetition of the title.

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

Completeness3/5

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

An output schema exists and annotations cover the safety profile, so the description is close to sufficient. Gaps remain around preconditions (project registration/auto-detect interaction between repo and project_number) and duplicate-item behavior for a mutation that is declared idempotent.

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?

Schema coverage is 80%, so most parameters are already documented, including auto-detect behavior for repo/owner and the optionality of project_number. The description adds only that issue_number may refer to a PR as well as an issue; it adds no format or resolution guidance beyond the schema.

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?

States a specific verb ('Add') and resource ('an existing GitHub Issue or Pull Request to a Kanban board'), and pins the backend as GitHub Project v2. The word 'existing' implicitly separates it from creation-flavored siblings like create_github_issue_with_entry, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'add an existing Issue or PR' — the issue must already exist, and the target is a Kanban board. There is no explicit when-to-use versus move_kanban_item or get_kanban_board, and no stated precondition such as registering the project first.

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