Skip to main content
Glama
saidsef

GitHub PR Issue Analyser

by saidsef

create_release

Create a new release in a GitHub repository by specifying tag name, release name, and description to organize and distribute software versions.

Instructions

Creates a new release in the specified GitHub repository. Args: repo_owner (str): The owner of the repository. repo_name (str): The name of the repository. tag_name (str): The tag name for the release. release_name (str): The name of the release. body (str): The description or body content of the release. Returns: Dict[str, Any]: The JSON response from the GitHub API containing release information if successful. None: If an error occurs during the release creation process. Error Handling: Logs errors and prints the traceback if the release creation fails, returning None.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_ownerYes
repo_nameYes
tag_nameYes
release_nameYes
bodyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function implementing the 'create_release' tool. It creates a new GitHub release by posting to the GitHub API with the provided repository details, tag, name, and body.
    def create_release(self, repo_owner: str, repo_name: str, tag_name: str, release_name: str, body: str) -> Dict[str, Any]:
        """
        Creates a new release in the specified GitHub repository.
        Args:
            repo_owner (str): The owner of the repository.
            repo_name (str): The name of the repository.
            tag_name (str): The tag name for the release.
            release_name (str): The name of the release.
            body (str): The description or body content of the release.
        Returns:
            Dict[str, Any]: The JSON response from the GitHub API containing release information if successful.
            None: If an error occurs during the release creation process.
        Error Handling:
            Logs errors and prints the traceback if the release creation fails, returning None.
        """
        logging.info(f"Creating release {release_name} in {repo_owner}/{repo_name}")
    
        # Construct the releases URL
        releases_url = f"https://api.github.com/repos/{repo_owner}/{repo_name}/releases"
    
        try:
            # Create the release
            response = requests.post(releases_url, headers=self._get_headers(), json={
                'tag_name': tag_name,
                'name': release_name,
                'body': body,
                'draft': False,
                'prerelease': False,
                'generate_release_notes': True
            }, timeout=TIMEOUT)
            response.raise_for_status()
            release_data = response.json()
    
            logging.info("Release created successfully")
            return release_data
    
        except Exception as e:
            logging.error(f"Error creating release: {str(e)}")
            traceback.print_exc()
            return {"status": "error", "message": str(e)}
  • The registration code that dynamically registers all public methods of the GitHubIntegration instance (including create_release) as MCP tools via FastMCP.add_tool.
        self.register_tools(self.gi)
        self.register_tools(self.ip)
    
    def register_tools(self, methods: Any = None) -> None:
        for name, method in inspect.getmembers(methods):
            if (inspect.isfunction(method) or inspect.ismethod(method)) and not name.startswith("_"):
                self.mcp.add_tool(method)
  • Documentation in the MCP server instructions mentioning the create_release tool.
    - Use create_tag and create_release for release management
  • Instantiation of the GitHubIntegration class whose methods are registered as tools.
    self.gi = GI()
  • Import of the GitHubIntegration class containing the create_release handler.
    from .github_integration import GitHubIntegration as GI
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by describing the return structure (Dict[str, Any] or None) and error handling behavior (logs errors, prints traceback, returns None). However, it doesn't mention authentication requirements, rate limits, whether this is a destructive operation, or what happens if the tag already exists - important context for a GitHub API tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (Args, Returns, Error Handling) and front-loads the core purpose. Every sentence serves a purpose, though the error handling section could be slightly more concise. The structure helps the agent quickly parse the information without unnecessary verbiage.

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 the complexity of a GitHub release creation tool with 5 parameters and no annotations, the description does well by documenting parameters, return values, and error handling. The presence of an output schema means the description doesn't need to detail return structure. However, it lacks some GitHub-specific context like authentication requirements or rate limiting considerations that would be helpful for the agent.

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 (titles only, no descriptions), the description provides excellent parameter semantics. It clearly documents all 5 parameters with their types and purposes, adding significant value beyond what the schema provides. The parameter documentation is comprehensive and explains what each argument represents in the GitHub context.

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 clearly states the specific action ('Creates a new release') and resource ('in the specified GitHub repository'), distinguishing it from sibling tools like create_issue or create_pr. It provides a complete verb+resource+context combination that leaves no ambiguity about what this tool does.

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 about when to use this tool versus alternatives. While it's clear this creates releases, there's no mention of prerequisites (e.g., existing tags), when to choose this over similar operations, or what constitutes appropriate usage contexts. The agent must infer usage from the tool name alone.

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/saidsef/mcp-github-pr-issue-analyser'

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