Skip to main content
Glama

jira_get_project_versions

Retrieve all versions for a Jira project to populate fixVersions and affectsVersions fields when creating or updating issues.

Instructions

Get all versions for a project - use this to find valid values for fixVersions and affectsVersions fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesProject key to get versions for

Implementation Reference

  • Main execution handler for the jira_get_project_versions tool. Parses input arguments using the schema and delegates to JiraClient.getProjectVersions, returning the result as JSON.
    case "jira_get_project_versions": {
      const { projectKey } = GetProjectVersionsSchema.parse(args);
      const versions = await jiraClient.getProjectVersions(projectKey);
      return {
        content: [{ type: "text", text: JSON.stringify(versions, null, 2) }],
      };
    }
  • Zod input schema for validating the tool's projectKey parameter.
    const GetProjectVersionsSchema = z.object({
      projectKey: z.string().describe("Project key to get versions for"),
    });
  • src/index.ts:490-504 (registration)
    Tool descriptor returned by ListToolsRequestHandler, including name, description, and input schema.
    {
      name: "jira_get_project_versions",
      description:
        "Get all versions for a project - use this to find valid values for fixVersions and affectsVersions fields",
      inputSchema: {
        type: "object",
        properties: {
          projectKey: {
            type: "string",
            description: "Project key to get versions for",
          },
        },
        required: ["projectKey"],
      },
    },
  • JiraClient helper method implementing the core logic: REST API call to fetch versions for the given projectKey.
      projectKey: string
    ): Promise<
      Array<{ id: string; name: string; released: boolean; archived: boolean }>
    > {
      return this.request<
        Array<{ id: string; name: string; released: boolean; archived: boolean }>
      >(`/project/${projectKey}/versions`);
    }
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. It mentions the tool retrieves data ('Get all versions'), implying a read operation, but doesn't address permissions, rate limits, pagination, or error conditions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that front-loads the core purpose and follows with usage guidance. Every word earns its place with no redundancy or unnecessary elaboration.

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

Completeness3/5

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

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is adequate but minimal. It covers purpose and usage context but lacks behavioral details that would be helpful for a read operation in a system like Jira. The absence of output schema means the description doesn't explain return values, which is a gap.

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?

Schema description coverage is 100%, so the schema already documents the single parameter 'projectKey'. The description doesn't add any additional semantic context about the parameter beyond what's in the schema, such as format examples or constraints. Baseline 3 is appropriate when the schema handles parameter documentation.

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 ('Get all versions') and resource ('for a project'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'jira_get_project' or 'jira_get_project_components', but the specific focus on versions is clear enough for basic distinction.

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?

The description provides explicit guidance on when to use this tool: 'to find valid values for fixVersions and affectsVersions fields'. This gives a clear context for usage, though it doesn't mention when NOT to use it or name specific alternatives among the siblings.

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/yogeshhrathod/JiraMCP'

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