Skip to main content
Glama
albertor03

Jira QMetry MCP Server

by albertor03

Update a Qmetry test cycle

update-qmetry-test-cycle

Update an existing test cycle by modifying its summary, project, folder, status, dates, or linked test cases.

Instructions

Update an existing test cycle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRefer id from the response of API "Search Test Cycles"
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 to user
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
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
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?

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, permission requirements, or error conditions. It only states 'update' with no further detail.

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

Conciseness3/5

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

The description is extremely concise at one sentence, but lacks structure and completeness. It could benefit from a brief overview of what can be updated or how the update works.

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?

With 16 parameters and no output schema, the description is too sparse to provide adequate context. It does not explain partial update behavior, required fields, or typical usage patterns.

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 each parameter thoroughly. The tool description adds no additional semantic information beyond what is in the schema, but the baseline of 3 is appropriate.

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 'Update an existing test cycle', which is a specific verb and resource. It distinguishes from sibling tools like create, delete, archive, etc. However, it lacks detail on what aspects can be updated.

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 is provided on when to use this tool versus alternatives, or any prerequisites or constraints. The description does not help the agent decide between this and sibling update tools.

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