Skip to main content
Glama

Git Tag

git_tag

Manage Git tags to mark releases and milestones. Create annotated or signed tags at specific commits, list existing versions, or delete obsolete tags to organize repository history.

Instructions

Manage tags: list all tags, create a new tag, or delete a tag. Tags are used to mark specific points in history (releases, milestones).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to the Git repository. Defaults to session working directory set via git_set_working_dir..
modeNoThe tag operation to perform.list
tagNameNoTag name for create/delete operations.
commitNoCommit to tag (default: HEAD for create operation).
messageNoTag message (creates annotated tag). For release tags, summarize the notable changes.
annotatedNoCreate annotated tag. Automatically set to true when message is provided.
signNoSign the commit/tag with GPG.
forceUnsignedOnFailureNoIf GPG/SSH signing fails, retry the tag creation without signing instead of failing.
forceNoForce tag creation/deletion (overwrite existing).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesIndicates if the operation was successful.
modeYesOperation mode that was performed.
tagsNoList of tags (for list mode).
createdNoCreated tag name (for create mode).
deletedNoDeleted tag name (for delete mode).
Behavior3/5

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

The description acknowledges mutability (create/delete) which aligns with readOnlyHint:false. However, it fails to disclose behavioral nuances beyond the schema, such as the destructive nature of force deletion, GPG signing failure behaviors, or that list is non-destructive while other modes mutate state.

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?

Extremely efficient two-sentence structure. The first sentence front-loads the available operations; the second provides semantic context. No redundant or wasted language.

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

Completeness4/5

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

Given 100% schema coverage and the presence of an output schema, the description adequately covers the tool's purpose. It could be improved by mentioning the default 'list' mode behavior or the relationship between the message and annotated parameters, but these are discoverable in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema has 100% coverage, the description adds valuable conceptual context by explaining tags mark 'releases' and 'milestones,' which helps agents understand the semantics of the tagName and message parameters for annotated tags.

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 explicitly states the three operations (list, create, delete) and the resource (tags). It clearly distinguishes this from sibling tools like git_branch or git_commit by defining tags as markers for 'specific points in history (releases, milestones)'.

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?

Provides clear context on the semantic purpose of tags (marking releases, milestones), which implies when to use the tool versus alternatives like branches. However, it lacks explicit guidance on when to choose between list/create/delete modes or warnings about delete implications.

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/cyanheads/git-mcp-server'

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