gh-board-mcp

list_activities

Retrieve draft items from a board using filters. Filter by status or priority to find specific tasks, such as 'Todo' or 'High', within a project.

Instructions

List activities (draft items) in a board. Filter by status and/or priority. Valid values depend on the project (new boards: Todo, In Progress, Done / Urgent, High, Medium, Low).

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": {
      "projectNumber": "<projectNumber>"
    },
    "name": "list_activities"
  }
}

Input Schema

Name	Required	Description
`status`	No	Status filter. Valid values depend on the project (new boards: Todo, In Progress, Done / Urgent, High, Medium, Low).
`priority`	No	Priority filter. Valid values depend on the project (new boards: Todo, In Progress, Done / Urgent, High, Medium, Low).
`projectNumber`	Yes	Number of the GitHub Project board

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 18, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must communicate behavioral traits. The verb 'list' implies a read operation, but the description does not explicitly state that it is read-only, safe, or idempotent. It also omits any mentions of authentication requirements or rate limits.

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 two sentences long, front-loaded with the core purpose, and efficiently adds filtering details. Every sentence contributes value without unnecessary elaboration.

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?

The description adequately explains what the tool does and how to filter, but it does not describe the return format or output structure. Since there is no output schema, the description should provide some context about what fields are returned, which is missing.

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 description coverage is 100%, so the schema already documents each parameter. The description adds no new parameter-level meaning beyond restating the valid values note already present in the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action ('List'), the resource ('activities (draft items)'), and the scope ('in a board'). It also mentions filtering by status and/or priority, which distinguishes it from sibling tools like list_projects or create_activity.

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

Usage Guidelines4/5

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

The description provides guidance on when to use the tool (listing activities with optional filters) and gives valid values for status/priority. However, it does not explicitly state when not to use it or mention alternative tools for similar tasks.

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

Deploy Server