GitHub MCP Server

list_project_v2_items

Retrieve items from a GitHub Project V2, including issues, pull requests, and draft items, to track project progress and manage tasks.

Instructions

List items in a Project V2 (issues, PRs, and draft 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": {
      "owner": "<owner>",
      "project_number": "<project_number>"
    },
    "name": "list_project_v2_items"
  }
}

Input Schema

Name	Required	Description	Default
`owner`	Yes	Organization or username
`project_number`	Yes	Project number
`owner_type`	No	Owner type (organization, user)	organization
`first`	No	Number of items to return (max 100)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 8, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool lists items but doesn't cover critical aspects like pagination behavior (implied by 'first' parameter but not explained), rate limits, authentication requirements, or whether it's read-only. This leaves significant gaps for an agent.

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?

The description is a single, efficient sentence that front-loads the core purpose with zero waste. Every word earns its place by specifying the resource and item types clearly.

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?

Given the tool has an output schema (which handles return values) and 100% schema coverage, the description is minimally adequate. However, with no annotations and a mutation-heavy sibling set (e.g., 'create_issue', 'update_pull_request'), it should more explicitly state this is a read operation to avoid confusion, making it incomplete for optimal agent use.

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 schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters (e.g., how 'owner_type' interacts with 'owner'). Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('List') and resource ('items in a Project V2'), specifying the types of items included ('issues, PRs, and draft items'). It distinguishes from general project listing tools like 'list_projects_v2' but doesn't explicitly differentiate from other item-listing tools in the sibling list, which is why it's not a 5.

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, such as 'list_issues' or 'list_pull_requests' for specific item types, or prerequisites like authentication. It simply states what it does without context.

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

Deploy Server