Skip to main content
Glama

create_release

Create a new release in a GitHub repository to package and distribute software versions with tags, descriptions, and optional draft or prerelease status.

Instructions

Create a new release in a GitHub repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
tag_nameYesThe name of the tag
target_commitishNoSpecifies the commitish value that determines where the Git tag is created from
nameNoThe name of the release
bodyNoText describing the release
draftNotrue to create a draft (unpublished) release, false to create a published one
prereleaseNotrue to identify the release as a prerelease, false to identify it as a full release
generate_release_notesNoWhether to automatically generate the name and body for this release

Implementation Reference

  • The core handler function that executes the create_release tool by sending a POST request to GitHub Releases API and parsing the response.
    export async function createRelease(
      github_pat: string,
      owner: string,
      repo: string,
      options: Omit<z.infer<typeof CreateReleaseSchema>, "owner" | "repo" | "github_pat">
    ): Promise<z.infer<typeof ReleaseSchema>> {
      const response = await githubRequest(
        github_pat,
        `https://api.github.com/repos/${owner}/${repo}/releases`,
        {
          method: "POST",
          body: options,
        }
      );
      return ReleaseSchema.parse(response);
    }
  • Input schema for the create_release tool, defining parameters like owner, repo, tag_name, etc.
    export const CreateReleaseSchema = z.object({
      owner: z.string().describe("Repository owner (username or organization)"),
      repo: z.string().describe("Repository name"),
      tag_name: z.string().describe("The name of the tag"),
      target_commitish: z.string().optional().describe("Specifies the commitish value that determines where the Git tag is created from"),
      name: z.string().optional().describe("The name of the release"),
      body: z.string().optional().describe("Text describing the release"),
      draft: z.boolean().optional().describe("true to create a draft (unpublished) release, false to create a published one"),
      prerelease: z.boolean().optional().describe("true to identify the release as a prerelease, false to identify it as a full release"),
      generate_release_notes: z.boolean().optional().describe("Whether to automatically generate the name and body for this release")
    });
  • src/index.ts:165-168 (registration)
    Registration of the create_release tool in the MCP server tool list.
      name: "create_release",
      description: "Create a new release in a GitHub repository",
      inputSchema: zodToJsonSchema(releases.CreateReleaseSchema),
    },
  • Dispatch handler case in the main CallToolRequestSchema handler that parses arguments and calls the createRelease function.
    case "create_release": {
      const args = releases._CreateReleaseSchema.parse(params.arguments);
      const { github_pat, owner, repo, ...options } = args;
      const result = await releases.createRelease(github_pat, owner, repo, options);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Extended schema including github_pat, used internally for parsing arguments.
    export const _CreateReleaseSchema = CreateReleaseSchema.extend({
      github_pat: z.string().describe("GitHub Personal Access Token"),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'create' implies a write operation, it doesn't disclose important behavioral traits like required permissions, whether this creates a public/private release by default, rate limits, or what happens on success/failure. The description is minimal and lacks operational context.

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 perfectly concise at 7 words - a single sentence that states the core purpose without any wasted words. It's front-loaded with the essential information and has no unnecessary elaboration.

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?

For a mutation tool with 9 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address what the tool returns, error conditions, authentication requirements, or how it differs from related creation tools. The combination of mutation behavior and rich parameter set demands more contextual information than provided.

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?

With 100% schema description coverage, the input schema already documents all 9 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters like how 'tag_name' relates to 'target_commitish' or the implications of 'draft' vs 'prerelease' settings.

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

Purpose4/5

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

The description clearly states the action ('create') and resource ('new release in a GitHub repository'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'create_tag' or 'upload_release_asset', which could create confusion about when to use each specific creation tool.

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 like 'create_tag' or 'upload_release_asset', nor does it mention prerequisites or context for creating releases. It simply states what the tool does without any usage context or decision criteria.

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/MissionSquad/mcp-github'

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