Skip to main content
Glama
mcp-github-project-manager

mcp-github-project-manager

by kunwarVivek

Manage Projects

manage_project
Destructive

Create, update, and organize GitHub Projects v2, including fields, views, items, templates, and repository or team links, by selecting an operation with the action field.

Instructions

Manage GitHub Projects (v2): create, list, get, update, delete projects; manage readme, fields, views, items; handle templates and link to repos/teams. Use the action field to select the operation.

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": {
      "action": "<action>"
    },
    "name": "manage_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNo
nameNo
repoNo
typeNoType of the field to create — exactly the types GitHub's ProjectV2CustomFieldType accepts
afterNo
firstNo
limitNo
ownerNo
titleNo
valueNo
actionYesThe project operation to perform
closedNoupdate: true closes the project, false reopens it
cursorNoCursor from a previous page's `nextCursor`; omit for the first page
filterNo
itemIdNo
layoutNoLayout of the view — exactly the layouts GitHub's ProjectV2ViewLayout accepts
readmeNo
statusNo
viewIdNo
afterIdNo
fieldIdNo
optionsNo
requiredNo
teamSlugNo
contentIdNo
projectIdNo
visibilityNo
contentTypeNo
descriptionNo
targetOwnerNo
collaboratorsNoThe collaborators to grant a role to, one entry per user or team
idempotencyKeyNoIdempotency key (1-128 chars) for create actions: retrying with the same key and arguments returns the first result instead of creating a duplicate; reusing it with different arguments is an error. Kept for 24 hours.
shortDescriptionNo
includeDraftIssuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.0.0
    • addedInput schema / properties / closed
      Added value: +{
      +  "description": "update: true closes the project, false reopens it",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Cursor from a previous page's `nextCursor`; omit for the first page",
      +  "type": "string"
      +}
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "description": "Idempotency key (1-128 chars) for create actions: retrying with the same key and arguments returns the first result instead of creating a duplicate; reusing it with different arguments is an error. Kept for 24 hours.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Addedv3.0.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the high-level safety profile is known. The description lists operation categories including delete and remove, but it does not disclose action-level behavior such as which actions are destructive versus read-only, what permissions are required, whether operations are reversible, or how partial failures behave.

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

Conciseness4/5

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

The description is two sentences and front-loads the core purpose before listing operation categories. It is compact and avoids filler, though the long run-on operation list becomes hard to parse for a tool with 38 actions.

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?

This is a high-complexity tool with 34 parameters, 38 enum actions, nested objects, and destructive behavior, but the description never explains action-specific requirements or side effects. The annotations cover general safety hints, yet the description remains too thin for an agent to invoke most actions correctly without studying the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 34 parameters, 21% schema description coverage, and only the `action` field mentioned in the description, the definition provides almost no parameter meaning beyond the schema. It does not map actions to required or optional parameters, explain nested objects like `filter` or `collaborators`, or clarify when fields such as `org`, `owner`, `projectId`, and `contentId` are needed.

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 names a specific resource, GitHub Projects v2, and lists the main operations: create, list, get, update, delete, plus readme, fields, views, items, templates, and repo/team links. This distinguishes it from issue-, PR-, and label-oriented siblings, but it does not explicitly name sibling tools or clarify edge cases where a project operation overlaps with those tools.

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 only usage guidance is 'Use the `action` field to select the operation,' which restates the required schema field rather than explaining when to choose this tool over alternatives. It gives no guidance on choosing among the 38 actions, no when-not-to-use conditions, and no prerequisites for destructive or permission-sensitive operations.

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