qmetry_fetch_test_suites_for_test_case

Get test suites that can be linked to test cases in QMetry with automatic viewId resolution 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") - tsFolderID (number) *required*: Test Suite folder ID (required for fetching test suites). This is the numeric identifier for the test suite folder. IMPORTANT: Get from project info response → rootFolders.TS.id (e.g., 113557 for MAC project). Use FETCH_PROJECT_INFO tool first to get this ID if not provided by user. For root folder: use rootFolders.TS.id, for sub-folders: use specific folder IDs. - viewId (number): ViewId for test suite folders - SYSTEM AUTOMATICALLY RESOLVES THIS. Leave empty unless you have a specific viewId. System will fetch project info using the projectKey and extract latestViews.TSFS.viewId automatically. Manual viewId only needed if you want to override the automatic resolution. - start (number): Start index for pagination - defaults to 0 (default: 0) - page (number): Page number to return (starts from 1) (default: 1) - limit (number): Number of records (default 10). (default: 10) - getColumns (boolean): Whether to get column information in response. (default: true) - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") Output Description: JSON object with test suites array and pagination metadata Use Cases: 1. Get test suites available for linking with test cases 2. Find appropriate test suites for test case organization 3. Browse test suites in specific folders for better management 4. Filter test suites by release, cycle, or archive status 5. Organize test execution by grouping test cases into test suites 6. Plan test suite structure for comprehensive test coverage 7. Manage test case categorization for reporting purposes 8. Search for existing test suites before creating new ones 9. Get root test suite folder contents using project info Examples: 1. Get test suites from root folder using auto-resolved viewId json { "tsFolderID": 113557 } Expected Output: List of test suites available in the root test suite folder with auto-resolved viewId 2. Get test suites with custom pagination and auto-resolved viewId json { "tsFolderID": 113557, "page": 1, "limit": 25 } Expected Output: Paginated list of test suites with 20 items per page 3. Filter test suites by release with auto-resolved viewId json { "tsFolderID": 113557, "filter": "[{\"type\":\"list\",\"value\":[55178],\"field\":\"release\"}]" } Expected Output: Test suites associated with Release 8.12 (ID: 55178) 4. Filter test suites by cycle with auto-resolved viewId json { "tsFolderID": 113557, "filter": "[{\"type\":\"list\",\"value\":[111577],\"field\":\"cycle\"}]" } Expected Output: Test suites associated with Cycle 8.12.1 (ID: 111577) 5. Get only active (non-archived) test suites json { "tsFolderID": 113557, "filter": "[{\"value\":[0],\"type\":\"list\",\"field\":\"isArchived\"}]" } Expected Output: List of active test suites (not archived) 6. Filter test suites by release and cycle json { "tsFolderID": 113557, "filter": "[{\"type\":\"list\",\"value\":[55178],\"field\":\"release\"},{\"type\":\"list\",\"value\":[111577],\"field\":\"cycle\"}]" } Expected Output: Test suites associated with both Release 8.12 (ID: 55178) and Cycle 8.12.1 (ID: 111577) 7. Get test suites with column information json { "tsFolderID": 113557, "getColumns": true } Expected Output: Test suites list with detailed column metadata for better interpretation 8. Search test suites from specific sub-folder with manual viewId json { "tsFolderID": 42, "viewId": 104316 } Expected Output: Test suites available in specific folder ID 42 for test case linking Hints: 1. CRITICAL: tsFolderID is REQUIRED - Test Suite folder ID will be auto-resolved if not provided 2. viewId will be AUTOMATICALLY RESOLVED from project info if not provided 3. HOW TO GET tsFolderID: 4. 1. Call FETCH_PROJECT_INFO tool first to get project configuration 5. 2. From the response, use rootFolders.TS.id for the root test suite folder 6. 3. Example: rootFolders.TS.id = 113557 (MAC project root TS folder) 7. 4. If user doesn't specify tsFolderID, automatically use rootFolders.TS.id from project info 8. VIEWID AUTO-RESOLUTION: 9. 1. System automatically fetches project info using the projectKey 10. 2. Extracts latestViews.TSFS.viewId automatically 11. 3. Example: latestViews.TSFS.viewId = 104316 (MAC project TSFS view) 12. 4. Manual viewId only needed if you want to override the automatic resolution 13. WORKFLOW: System automatically handles project info if tsFolderID or viewId is not provided 14. PROJECT INFO STRUCTURE: clientData.rootFolders.TS.id contains the root test suite folder ID 15. PROJECT INFO STRUCTURE: latestViews.TSFS.viewId contains the test suite folder view ID 16. For sub-folders: Use specific folder IDs if you know them, or call folder listing APIs 17. FILTER CAPABILITIES: Same as other QMetry list operations 18. FILTER FIELDS: release, cycle, isArchived, name, status, priority 19. RELEASE/CYCLE FILTERING: Use numeric IDs in list format (get from FETCH_RELEASES_AND_CYCLES) 20. ARCHIVE FILTERING: 0=Active, 1=Archived 21. getColumns=true provides additional metadata for result interpretation 22. Multiple filter conditions are combined with AND logic 23. Pagination supported for large result sets (start, page, limit parameters) 24. This tool helps organize test cases into logical test suites 25. Essential for test execution planning and test case management 26. Use this before creating new test suites to check existing ones. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

qmetry_fetch_test_suites_for_test_case accepts 9 parameters: page, limit, start, filter, viewId, baseUrl, getColumns, projectKey, tsFolderID. Required: tsFolderID. The full parameter table on this page comes from the server's own tool schema.

Register the SmartBear MCP server in PolicyLayer and add a rule for qmetry_fetch_test_suites_for_test_case: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches SmartBear MCP. Nothing to install.

qmetry_fetch_test_suites_for_test_case is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Yes. Add a rate_limit block to the qmetry_fetch_test_suites_for_test_case rule in your PolicyLayer 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 PolicyLayer policy for qmetry_fetch_test_suites_for_test_case. 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_fetch_test_suites_for_test_case is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.