qmetry_create_release

Create a new release in QMetry with optional cycle for test planning and execution tracking **Parameters:** - projectKey (string): Project key - unique identifier for the project (default: "default") - baseUrl (string): The base URL for the QMetry instance (must be a valid URL) (default: "https://testmanagement.qmetry.com") - release (object) *required* - cycle (object): Optional cycle to create within the release **Output Description:** JSON object containing the created release ID, release details, and cycle information if provided **Use Cases:** 1. Create a new release for a major product version (e.g., v2.0, Q1 Release) 2. Create a release with an initial cycle for immediate test planning 3. Set up release dates for sprint planning and milestone tracking 4. Organize test execution by product versions and cycles 5. Create release hierarchy for better test planning and reporting 6. Establish test execution phases with releases and cycles **Examples:** 1. Create a basic release with just a name ```json { "release": { "name": "Release 2.0" } } ``` Expected Output: Release 'Release 2.0' created successfully with generated release ID 2. Create a release with description and dates ```json { "release": { "name": "Q1 2024 Release", "description": "First quarter release for 2024", "startDate": "01-01-2024", "targetDate": "31-03-2024" } } ``` Expected Output: Release 'Q1 2024 Release' created with start date 01-01-2024 and target date 31-03-2024 3. Create a release with an initial cycle ```json { "release": { "name": "Release 3.0", "description": "Major product update" }, "cycle": { "name": "Sprint 1", "isLocked": false, "isArchived": false } } ``` Expected Output: Release 'Release 3.0' created with cycle 'Sprint 1' for test execution planning 4. Create a release with all details ```json { "release": { "name": "Summer 2024 Release", "description": "Summer product release with new features", "startDate": "01-06-2024", "targetDate": "31-08-2024" }, "cycle": { "name": "Beta Testing Cycle", "isLocked": false } } ``` Expected Output: Release 'Summer 2024 Release' created with dates and 'Beta Testing Cycle' for test execution **Hints:** 1. CRITICAL: release.name is REQUIRED - must provide a name for the release 2. Date format depends on QMetry instance configuration: DD-MM-YYYY or MM-DD-YYYY 3. Check your QMetry instance settings to determine the correct date format 4. If dates are in wrong format, QMetry will return an error - verify format with admin 5. projectID is optional in the release object - it will be auto-resolved from the project key if not provided 6. To explicitly set projectID, first call FETCH_PROJECT_INFO to get the numeric project ID 7. cycle parameter is completely optional - omit it if you only want to create a release 8. If providing cycle, cycle.name is REQUIRED 9. cycle.isLocked defaults to false if not provided - set to true to prevent modifications 10. cycle.isArchived defaults to false if not provided - set to true to archive immediately (rare) 11. Releases can have multiple cycles added later using other tools 12. Use descriptive release names like 'Release 2.0', 'Q1 2024', 'Sprint 15' for better organization 13. startDate and targetDate help with sprint planning and milestone tracking 14. Creating a release with a cycle is useful for immediate test planning after release creation 15. Release hierarchy: Project → Release → Cycle → Test Execution 16. After creating a release, you can associate test suites and test cases with it 17. Use FETCH_RELEASES_CYCLES tool after creation to verify the release was created successfully. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

Add a rule in your Intercept YAML policy under the tools section for qmetry_create_release. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

qmetry_create_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Yes. Add a rate_limit block to the qmetry_create_release rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

Set action: deny in the Intercept policy for qmetry_create_release. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

qmetry_create_release is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.