Skip to main content
Glama
ko1ynnky

GitHub Actions MCP Server

by ko1ynnky

list_workflows

Lists GitHub Actions workflows for a repository to view, manage, and understand automation processes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
pageNoPage number for pagination
perPageNoResults per page (max 100)

Implementation Reference

  • The handler function that lists workflows in a GitHub repository by making an API request to the GitHub Actions workflows endpoint and parsing the response.
    export async function listWorkflows(
      owner: string, 
      repo: string, 
      page?: number, 
      perPage?: number
    ) {
      owner = validateOwnerName(owner);
      repo = validateRepositoryName(repo);
    
      const url = buildUrl(`https://api.github.com/repos/${owner}/${repo}/actions/workflows`, {
        page: page,
        per_page: perPage
      });
    
      const response = await githubRequest(url);
      return WorkflowsSchema.parse(response);
    }
  • Zod schema defining the input parameters for the list_workflows tool: owner, repo, optional page and perPage.
    export const ListWorkflowsSchema = z.object({
      owner: z.string().describe("Repository owner (username or organization)"),
      repo: z.string().describe("Repository name"),
      page: z.number().optional().describe("Page number for pagination"),
      perPage: z.number().optional().describe("Results per page (max 100)"),
    });
  • src/index.ts:147-156 (registration)
    MCP server tool registration for 'list_workflows', providing the schema and an async handler that logs the request, calls the listWorkflows function, and returns the result as JSON text content.
    server.tool(
        "list_workflows",
        actions.ListWorkflowsSchema.shape,
        async (request: any) => {
          logToFile('[MCP Server Log] Received list_workflows request (via server.tool)');
          // Args are already parsed by the McpServer using the provided schema
          const result = await actions.listWorkflows(request.owner, request.repo, request.page, request.perPage);
          return { content: [{ type: "text", text: JSON.stringify(result) }] };
        }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/ko1ynnky/github-actions-mcp-server'

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