Skip to main content
Glama
albertor03

Jira QMetry MCP Server

by albertor03

Create a Qmetry test cycle

create-qmetry-test-cycle

Create a new test cycle in QMetry for Jira by specifying project, summary, and optional fields like dates, priority, and linked test cases.

Instructions

Create a new test cycle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsNoRefer ids from the response of API "Get Labels". Will be sent as {add: [labelId1, ...]} to API
statusNoRefer id from the response of API "Get Test Cycle Status"
summaryYesTest Cycle Summary
assigneeNoPass Jira user account uuid to assign test cycle
folderIdNoRefer id from the response of API "Get Test Cycle folders"
priorityNoRefer id from the response of API "Get Priorities"
reporterNoPass Jira user account uuid to assign reporter
projectIdYesRefer id from the response of API "Get QMetry Enabled Projects"
actualTimeNoEnter value in milliseconds
descriptionNoTest Cycle description
isAutomatedNoWhether test cycle is automated or not - true or false
customFieldsNoCustom fields as array of objects with id and value. Refer to "Get Test Cycle Custom Fields" to get available custom fields.
plannedEndDateNoEnter in format dd/MMM/yyyy HH:mm. Example: 25/Oct/2025 17:00
testCasesToLinkNoEither list of test case Ids or search filter query
plannedStartDateNoEnter in format dd/MMM/yyyy HH:mm. Example: 18/Oct/2025 09:00
Behavior2/5

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

Without annotations, the description carries full burden for behavioral disclosure. It does not mention permissions, side effects, or return value. For a creation tool, this is a significant gap.

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

Conciseness2/5

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

The description is a single sentence that is too minimal to be considered efficient. It repeats the tool's purpose without adding value, making it under-specified rather than concise.

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

Completeness1/5

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

Given the complexity (15 parameters, 2 required) and no output schema or annotations, the description is severely incomplete. It fails to explain what the tool does beyond its name, leaving the agent without enough context.

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 all parameters. The description adds no additional meaning beyond 'Create a new test cycle'. Baseline score of 3 applies.

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 'Create a new test cycle', with a specific verb and resource. However, it does not distinguish from sibling creation tools like clone- or copy- operations, which could lead to confusion.

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?

No guidance on when to use this tool versus alternatives such as clone-qmetry-test-cycle or update-qmetry-test-cycle. No context on prerequisites or typical use cases is provided.

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/albertor03/jira-qmetry-mcp'

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