publish-pilot-mcp

Overview Schema Source Related Servers Discussions Admin

tag_and_release

Creates a v tag, pushes branch and tag together, and generates the GitHub release from CHANGELOG unless release.yml handles it—without moving existing tags.

Instructions

Tag v, push branch and tag together, and create the GitHub release from CHANGELOG unless release.yml does. Never moves tags.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dir": "<dir>"
    },
    "name": "tag_and_release"
  }
}

Input Schema

Name	Required	Description	Default
`dir`	Yes
`version`	No
`createRelease`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.4.0Oct 26, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / createRelease / description

Removed value: -"Default: create the release here only when .github/workflows/release.yml doesn't create one. Pass true or false to force."

removedInput schema / properties / dir / description

Removed value: -"Project folder (absolute path, or relative to the server's working directory)."

removedInput schema / properties / version / description

Removed value: -"Must match the manifest; defaults to it."

Changed2 schema fields changedv0.3.0Oct 19, 2026

removedInput schema / properties / createRelease / default
```
Removed value: -false
```

changedInput schema / properties / createRelease / description

Previous value: -"Create the GitHub release here (repo-only projects). For 'both', release.yml creates it."New value: +"Default: create the release here only when .github/workflows/release.yml doesn't create one. Pass true or false to force."

First observedv0.1.0Oct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The phrase 'Never moves tags' is a crucial behavioral trait that informs the agent about the operation's safety profile beyond the 'destructiveHint: false' annotation. This prevents potential destructive tag manipulation.

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 single sentence is dense and highly efficient, front-loading the core functionality and immediately addressing key constraints and dependencies (like the release.yml logic).

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

Completeness5/5

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

It manages the complexity of a multi-step Git workflow (tag + push + release) in one place by defining the scope (everything except moves) and the release logic exception (release.yml).

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

Parameters5/5

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

With 0% schema description coverage, the description is critical. It adds semantics by clarifying that the versioning refers to 'v<manifest version>' and explicitly links the `createRelease` behavior to the existence of 'release.yml'.

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 specifies a concrete set of actions: tagging a version, pushing a branch and tag together, and creating a GitHub release. This clearly distinguishes it from simple commit or version bump tools.

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?

It explicitly mentions a conditional branch ('unless release.yml does'), guiding the agent on when the default release creation logic is skipped. While it doesn't explicitly state when NOT to use the tag functionality, the conditional logic provides clear usage context.

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