Skip to main content
Glama
Ryan0204

github-repo-mcp

getRepoAllDirectories

Browse and retrieve a complete list of directories within a GitHub repository by providing its URL. Simplify repository exploration for AI assistants with this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoUrlYesThe URL of the Github repo

Implementation Reference

  • index.ts:32-71 (handler)
    Handler function that parses the repo URL, fetches the root directory contents from GitHub using Octokit, formats the items as JSON, and returns them as text content or an error.
    async ({ repoUrl }, extra) => {
      try {
        const { owner, repo } = parseGitHubUrl(repoUrl);
        
        const { data } = await octokit.rest.repos.getContent({
          owner,
          repo,
          path: "",
        });
    
        // Format the response
        const items = Array.isArray(data) ? data.map(item => ({
          name: item.name,
          type: item.type,
          path: item.path,
        })) : [];
    
        const itemsDisplay = JSON.stringify(items, null, 2);
    
        return {
          content: [
            {
              type: "text",
              text: `Repository root contents for ${owner}/${repo}:\n\n${itemsDisplay}`,
            },
          ],
        };
      } catch (error) {
        console.error("Error fetching repo:", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching repo: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • index.ts:27-72 (registration)
    Registration of the 'getRepoAllDirectories' tool using server.tool(), including name, input schema, and inline handler.
    server.tool(
      "getRepoAllDirectories",
      {
        repoUrl: z.string().url().describe("The URL of the Github repo"),
      },
      async ({ repoUrl }, extra) => {
        try {
          const { owner, repo } = parseGitHubUrl(repoUrl);
          
          const { data } = await octokit.rest.repos.getContent({
            owner,
            repo,
            path: "",
          });
    
          // Format the response
          const items = Array.isArray(data) ? data.map(item => ({
            name: item.name,
            type: item.type,
            path: item.path,
          })) : [];
    
          const itemsDisplay = JSON.stringify(items, null, 2);
    
          return {
            content: [
              {
                type: "text",
                text: `Repository root contents for ${owner}/${repo}:\n\n${itemsDisplay}`,
              },
            ],
          };
        } catch (error) {
          console.error("Error fetching repo:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error fetching repo: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Input schema using Zod: repoUrl as a required URL string.
    {
      repoUrl: z.string().url().describe("The URL of the Github repo"),
    },
  • Helper function to parse GitHub repository URL into owner and repo name.
    function parseGitHubUrl(url: string) {
      const regex = /github\.com\/([^\/]+)\/([^\/]+)/;
      const match = url.match(regex);
      if (!match) {
        throw new Error("Invalid GitHub repository URL");
      }
      const [, owner, repo] = match;
      return { owner, repo: repo.replace(".git", "") };
    }
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

Related 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/Ryan0204/github-repo-mcp'

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