Skip to main content
Glama

list_project_columns

Retrieve and display all columns from a GitHub project to organize tasks and track workflow progress.

Instructions

List columns for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe ID of the project
per_pageNoResults per page (max 100)
pageNoPage number of the results

Implementation Reference

  • The core handler function that implements the logic to list project columns by querying the GitHub API and parsing the response with Zod.
    export async function listProjectColumns(
      github_pat: string,
      project_id: number,
      options: {
        per_page?: number;
        page?: number;
      } = {}
    ): Promise<z.infer<typeof ProjectColumnSchema>[]> {
      const url = new URL(`https://api.github.com/projects/${project_id}/columns`);
      
      if (options.per_page) url.searchParams.append("per_page", options.per_page.toString());
      if (options.page) url.searchParams.append("page", options.page.toString());
      
      const response = await githubRequest(
        github_pat,
        url.toString(),
        {
          headers: {
            "Accept": "application/vnd.github.inertia-preview+json",
          },
        }
      );
      return z.array(ProjectColumnSchema).parse(response);
    }
  • Input schema definitions for the list_project_columns tool, including parameters for project_id, pagination, and the internal schema with github_pat.
    export const ListProjectColumnsSchema = z.object({
      project_id: z.number().describe("The ID of the project"),
      per_page: z.number().optional().describe("Results per page (max 100)"),
      page: z.number().optional().describe("Page number of the results"),
    });
    
    export const _ListProjectColumnsSchema = ListProjectColumnsSchema.extend({
      github_pat: z.string().describe("GitHub Personal Access Token"),
    });
  • Output schema for individual project columns returned by the GitHub API.
    export const ProjectColumnSchema = z.object({
      id: z.number(),
      node_id: z.string(),
      url: z.string(),
      project_url: z.string(),
      cards_url: z.string(),
      name: z.string(),
      created_at: z.string(),
      updated_at: z.string(),
    });
  • src/index.ts:259-263 (registration)
    Tool registration in the MCP tools array, defining name, description, and input schema.
    {
      name: "list_project_columns",
      description: "List columns for a project",
      inputSchema: zodToJsonSchema(projects.ListProjectColumnsSchema),
    },
  • src/index.ts:703-710 (registration)
    Dispatcher case in the main request handler that parses arguments and calls the listProjectColumns implementation.
    case "list_project_columns": {
      const args = projects._ListProjectColumnsSchema.parse(params.arguments);
      const { github_pat, project_id, ...options } = args;
      const result = await projects.listProjectColumns(github_pat, project_id, options);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a list operation, implying read-only behavior, but doesn't disclose any behavioral traits like pagination details (implied by parameters), rate limits, authentication needs, or what the output looks like. This is a significant gap for a tool with parameters.

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 with zero waste. It's front-loaded and appropriately sized for a simple list tool, earning its place without unnecessary elaboration.

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 no annotations, no output schema, and 3 parameters, the description is incomplete. It doesn't explain the return values, pagination behavior, or any error conditions. For a list tool with pagination parameters, more context is needed to guide the agent effectively.

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 fully documents the parameters (project_id, per_page, page). The description adds no additional meaning beyond what's in the schema, such as explaining relationships or constraints. Baseline 3 is appropriate when 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 ('columns for a project'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_projects' or 'list_issues', which follow a similar pattern, so it misses full sibling distinction.

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. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name and parameters alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MissionSquad/mcp-github'

If you have feedback or need assistance with the MCP directory API, please join our Discord server