qmetry_fetch_test_case_executions

// WHEN AI AGENTS USE THIS TOOL

AI agents call qmetry_fetch_test_case_executions to retrieve information from SmartBear MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON QMETRY_FETCH_TEST_CASE_EXECUTIONS

Even though qmetry_fetch_test_case_executions only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

smartbear-mcp.yaml

tools:
  qmetry_fetch_test_case_executions:
    rules:
      - action: allow

See the full SmartBear MCP policy for all 147 tools.

// DETAILS

Tool Name qmetry_fetch_test_case_executions

Category Read

MCP Server SmartBear MCP MCP Server

Risk Level Low

// MORE SMARTBEAR MCP TOOLS

Destructive collaborator_delete_collaborator_remote_system_configuration Destructive reflect_cancel_suite_execution Destructive reflect_delete_previous_step Destructive swagger_delete_portal_product Destructive swagger_delete_table_of_contents Execute collaborator_reviewservice_action Execute contract-testing_can_i_deploy Execute qmetry_link_issues_to_testcase_run

View all 147 tools →

// RELATED READING

// FAQ

What does the qmetry_fetch_test_case_executions tool do? +

Get execution records for a specific test case by numeric ID **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") - tcid (number) *required*: Test Case numeric ID. This is the internal numeric identifier, not the entity key like 'MAC-TC-1684'. You can get this ID from test case search results or by using filters. - tcversion (number): Test Case version number (optional, defaults to 1). This is the internal numeric identifier for the version. - 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) - scope (string): Scope of the operation - defines the context for data retrieval. Common values: 'project' (default), 'folder', 'release', 'cycle'. Applies to any entity type being fetched or operated upon. (default: "project") - filter (string): Filter criteria as JSON string (default '[]') (default: "[]") **Output Description:** JSON object with executions array containing execution records, status, timestamps, and metadata **Use Cases:** 1. Get execution history for a specific test case 2. Retrieve test case execution results for reporting 3. Filter executions by test suite, platform, or execution status 4. Get execution data for test case analysis 5. Monitor test case execution trends over time 6. Filter executions by release, cycle, or execution date 7. Get execution details for specific test case versions 8. Audit test execution history for compliance 9. Analyze test case execution performance across different environments 10. Track test execution by specific users or teams **Examples:** 1. Get all executions for test case ID 1223922 ```json { "tcid": 1223922 } ``` Expected Output: List of execution records for test case with execution details, status, and metadata 2. Get executions for specific test case version ```json { "tcid": 1223922, "tcversion": 2 } ``` Expected Output: Execution records for version 2 of the test case 3. Filter executions by test suite and platform ```json { "tcid": 1223922, "filter": "[{\"value\":\"Sample Test Suite\",\"type\":\"string\",\"field\":\"testSuiteName\"},{\"value\":[12345],\"type\":\"list\",\"field\":\"platformID\"}]" } ``` Expected Output: Filtered execution records matching test suite and platform criteria 4. Filter executions by execution status ```json { "tcid": 1223922, "filter": "[{\"value\":[\"PASS\"],\"type\":\"list\",\"field\":\"executionStatus\"}]" } ``` Expected Output: Execution records with PASS status only 5. Filter executions by release and cycle ```json { "tcid": 1223922, "filter": "[{\"value\":[55178],\"type\":\"list\",\"field\":\"release\"},{\"value\":[111577],\"type\":\"list\",\"field\":\"cycle\"}]" } ``` Expected Output: Execution records filtered by specific release and cycle 6. Filter executions by date range ```json { "tcid": 1223922, "filter": "[{\"value\":\"2024-01-01\",\"type\":\"date\",\"field\":\"executedDate\",\"comparison\":\"gt\"},{\"value\":\"2024-12-31\",\"type\":\"date\",\"field\":\"executedDate\",\"comparison\":\"lt\"}]" } ``` Expected Output: Execution records within the specified date range 7. Filter executions by user ```json { "tcid": 1223922, "filter": "[{\"value\":[\"john.doe\"],\"type\":\"list\",\"field\":\"executedBy\"}]" } ``` Expected Output: Execution records executed by specific user **Hints:** 1. This API requires a numeric tcid parameter, not entity key 2. If user provides entityKey (e.g., MAC-TC-1684), first call FETCH_TEST_CASES with filter on entityKeyId to resolve the tcid 3. After resolving entityKey → tcid, call this tool with the resolved numeric tcid 4. tcversion parameter is optional - omit to get executions for all versions 5. 6. CRITICAL WORKFLOW FOR LINKED ISSUES: When user asks 'fetch linked issues of test case [ID]' or 'linked issues of execution': 7. YOU MUST FIRST get the execution data using this tool to extract tcRunID before fetching issues! 8. 9. COMPLETE WORKFLOW FOR TEST CASE → LINKED ISSUES: 10. STEP 1: Resolve Test Case ID (if needed) - Use FETCH_TEST_CASES if user provides entity key 11. STEP 2: Fetch Test Case Executions (THIS TOOL) - Input: tcid, Extract: data[].tcRunID values 12. STEP 3: Fetch Linked Issues - Tool: FETCH_LINKED_ISSUES_BY_TESTCASE_RUN, Input: entityId = tcRunID 13. 14. ID MAPPING CRITICAL UNDERSTANDING: 15. - tcid/tcID = Test Case ID (for getting execution data with this tool) 16. - tcRunID = Test Case Run/Execution ID (THIS is entityId for linked issues API) 17. - entityId = tcRunID (what the linked issues API actually needs) 18. 19. NEVER USE tcid DIRECTLY as entityId for linked issues! 20. ALWAYS get tcRunID from executions and use THAT as entityId! 21. 22. EXAMPLE RESPONSE STRUCTURE FROM THIS TOOL: 23. { "data": [{ "tcRunID": 58312120, "testSuiteName": "Suite 1", "executionStatus": "PASS" }] } 24. → Use tcRunID (58312120) as entityId for linked issues API 25. 26. FILTER CAPABILITIES: Support extensive filtering by test suite, platform, status, user, release, cycle, dates, and archive status 27. FILTER FIELDS: testSuiteName (string), platformID (list), executionStatus (list), executedBy (list), project (list), release (list), cycle (list), executedDate (date with comparison), isPlatformArchived (list), isTestSuiteArchived (list), executedVersion (numeric) 28. DATE FILTERING: Use 'gt' (greater than) and 'lt' (less than) comparisons for executedDate field 29. EXECUTION STATUS: Common values include 'PASS', 'FAIL', 'BLOCKED', 'NOT_EXECUTED', 'WIP' (verify with your QMetry instance) 30. PLATFORM/SUITE ARCHIVE: Use [1,0] for both archived and non-archived, [1] for archived only, [0] for active only 31. Multiple filter conditions are combined with AND logic 32. Use pagination for large execution result sets (start, page, limit parameters) 33. Get platform IDs from FETCH_PLATFORMS tool and release/cycle IDs from FETCH_RELEASES_AND_CYCLES tool 34. This tool is essential for test execution reporting, trend analysis, and compliance auditing 35. Execution data includes timestamps, user information, environment details, and test results 36. Use scope parameter to define retrieval context (project, folder, release, cycle). It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on qmetry_fetch_test_case_executions? +

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

What risk level is qmetry_fetch_test_case_executions? +

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

Can I rate-limit qmetry_fetch_test_case_executions? +

Yes. Add a rate_limit block to the qmetry_fetch_test_case_executions 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.

How do I block qmetry_fetch_test_case_executions completely? +

Set action: deny in the Intercept policy for qmetry_fetch_test_case_executions. 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.

What MCP server provides qmetry_fetch_test_case_executions? +

qmetry_fetch_test_case_executions 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.

qmetry_fetch_test_case_executions

Enforce policies on SmartBear MCP