Skip to main content
Glama

tag_list

List all tags in a Git repository by providing its absolute path. Enables efficient tag management via the Git MCP Server for streamlined version control workflows.

Instructions

List tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to repository. MUST be an absolute path (e.g., /Users/username/projects/my-repo)

Implementation Reference

  • The handler function `GitOperations.tagList` that validates the repository path, executes `git tag -l` command with caching, and returns the list of tags as text content.
    static async tagList(options: BasePathOptions, context: GitToolContext): Promise<GitToolResult> {
      const path = this.getPath(options);
      return await this.executeOperation(
        context.operation,
        path,
        async () => {
          const { path: repoPath } = PathValidator.validateGitRepo(path);
          const result = await CommandExecutor.executeGitCommand(
            'tag -l',
            context.operation,
            repoPath
          );
    
          const output = result.stdout.trim();
          return {
            content: [{
              type: 'text',
              text: output || 'No tags found'
            }]
          };
        },
        {
          useCache: true,
          stateType: RepoStateType.TAG,
          command: 'tag -l'
        }
      );
    }
  • The switch case in the tool executor that handles the 'tag_list' tool call by validating arguments and delegating to `GitOperations.tagList`.
    case 'tag_list': {
      const validArgs = this.validateArguments(operation, args, isPathOnly);
      return await GitOperations.tagList(validArgs, context);
    }
  • The tool registration definition including the name 'tag_list', description, and input schema specifying an optional repository path.
      name: 'tag_list',
      description: 'List tags',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: `Path to repository. ${PATH_DESCRIPTION}`,
          },
        },
        required: [],
      },
    },
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 of behavioral disclosure. 'List tags' implies a read-only operation, but it doesn't specify whether it requires a valid repository, what happens if the path is invalid, or the format of the output (e.g., list of tag names). This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with just two words ('List tags'), which efficiently conveys the core action and resource without any wasted words. It is front-loaded and appropriately sized for a simple tool.

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 the tool's moderate complexity (a list operation with one parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the return values, error conditions, or behavioral nuances, leaving the agent with insufficient context to use the tool effectively beyond basic inference.

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 input schema has 100% description coverage for its single parameter ('path'), so the schema already documents it well. The description adds no additional meaning about parameters beyond what the schema provides, such as clarifying the 'path' usage or default behavior when omitted. Baseline 3 is appropriate given high schema coverage.

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

Purpose3/5

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

The description 'List tags' clearly states the verb ('List') and resource ('tags'), making the basic purpose understandable. However, it lacks specificity about what kind of tags (e.g., Git tags) and doesn't distinguish from sibling tools like 'tag_create' or 'tag_delete' beyond the obvious list vs. create/delete 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. It doesn't mention prerequisites (e.g., needing a Git repository), exclusions, or context for choosing it over other tag-related tools like 'tag_create' or 'tag_delete'.

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/Sheshiyer/git-mcp-v2'

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