accueil / serveurs / Dev & Code / io.github.LambdaTest/mcp
io.github.LambdaTest/mcp
serveur MCP (Model Context Protocol) · MCP Lambdatest 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.LambdaTest/mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.LambdaTest/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 88 outils
- analyzeAppViaTunnel≈ 152 tokens
Analyzes a locally running app for accessibility via LambdaTest tunnel.
Paramètres, retour & exemple (3)
Paramètresport· number · requis
Port where the app is runningtunnelId· string · requis
Tunnel IDtunnelName· string · requis
Tunnel name
Exemple d'appel{"name": "analyzeAppViaTunnel", "arguments": {"port": 1, "tunnelId": "texte", "tunnelName": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - analyzeHyperExecuteJob≈ 182 tokens
Perform a full analysis of a HyperExecute job: fetches job info, sessions, traverses all tasks → scenario stages → console logs, and returns a structured report with test results, per-scenario logs, and pass/fail statistics. Use this for questions like "which tests failed and why" or "show me the console logs for job X".
Paramètres, retour & exemple (1)
ParamètresjobId· string · requis
The HyperExecute job ID to analyze
Exemple d'appel{"name": "analyzeHyperExecuteJob", "arguments": {"jobId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - answerHyperExecuteQuery≈ 136 tokens
Answers questions about HyperExecute features, configuration, usage, troubleshooting, and best practices by searching through documentation.
Paramètres, retour & exemple (1)
Paramètresquery· string · requis
Question about HyperExecute
Exemple d'appel{"name": "answerHyperExecuteQuery", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - automationQuery≈ 676 tokens
Read-only query of LambdaTest automation resources: list builds, get one build, list the sessions in a build, fetch test details, and retrieve test logs (command, network, console, selenium, instrumentation). Every combination works on platform "web" or "app": build list or get, session list or get, test get, and logs get with a logType. List results carry a pagination object; trust it, not result_set.total, which also counts older builds the list no longer returns. logType "instrumentation" returns XCUI and Espresso test logs. Renaming, stopping and deleting builds are separate tools: updateBuild, stopBuild and deleteBuild.
Paramètres, retour & exemple (14)
Paramètressort· string · optionnel
Sort order for build listing (e.g. "asc", "desc")limit· integer · optionnel
Number of results to return, 1 to 100action· string · requis · list | get
The read to perform: list, or get oneoffset· integer · optionnel
Offset for pagination; pass the next offset from a previous responsestatus· string · optionnel
Filter builds by status (e.g. "running", "passed", "failed")testId· string · optionnel
Test ID — required for test get and logs gettodate· string · optionnel
Filter builds to this date (YYYY-MM-DD, not before fromdate)buildId· number · optionnel
Build ID — required for build get, optional filter for session listlogType· string · optionnel · command | network | console | selenium | instrumentation
Log type — required when resource is "logs"fromdate· string · optionnel
Filter builds from this date (YYYY-MM-DD, a real calendar date)platform· string · requis · web | app
The platform type: "web" for browser automation, "app" for mobile app automationresource· string · requis · build | session | test | logs
The resource type to querysessionId· string · optionnel
Session ID: required for session get and for app platform log retrieval. Session get also accepts the test ID instead.pageNumber· integer · optionnel
Page number for command log pagination, from 1
Exemple d'appel{"name": "automationQuery", "arguments": {"action": "list", "platform": "web", "resource": "build"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - buildLocalAppForAnalysis≈ 226 tokens
Returns step-by-step instructions to build and serve a local web app and open a LambdaTest tunnel to it, so its accessibility can then be scanned with analyzeAppViaTunnel. It does not build, run or scan anything itself, and never includes the access key.
Paramètres, retour & exemple (3)
Paramètresport· number · requis
Port to host the app locallycodebasePath· string · requis
Absolute path to the codebase directorycustomBuildCommand· string · optionnel
Custom build command (optional, e.g., npm run build)
Exemple d'appel{"name": "buildLocalAppForAnalysis", "arguments": {"port": 1, "codebasePath": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - checkAppProcessingStatus≈ 277 tokens
Check whether an uploaded app has been processed and is ready for features like image injection, network logs, and screenshot unblock on real devices. The LambdaTest API has no read-only status call: this one starts or refreshes the processing for the requested features, so the app's last-updated time changes. An app id that is not among your uploaded apps returns an error.
Paramètres, retour & exemple (4)
ParamètresappId· string · requis
The app ID to checknetworkLogsEnabled· boolean · optionnel
Check network logs supportimageInjectionEnabled· boolean · optionnel
Check image injection supportscreenshotUnblockEnabled· boolean · optionnel
Check screenshot unblock support
Exemple d'appel{"name": "checkAppProcessingStatus", "arguments": {"appId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - deleteBuild≈ 126 tokens
Permanently deletes a LambdaTest web automation build and its test results. Cannot be undone.
Paramètres, retour & exemple (1)
ParamètresbuildId· number · requis
ID of the build to delete
Exemple d'appel{"name": "deleteBuild", "arguments": {"buildId": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - deletePrerunFile≈ 170 tokens
Delete an uploaded prerun file by stored LambdaTest file path.
Paramètres, retour & exemple (2)
ParamètresfilePath· string · optionnel
Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)file_path· string · optionnel
Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)
Exemple d'appel{"name": "deletePrerunFile", "arguments": {"filePath": "texte", "file_path": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - deleteSession≈ 114 tokens
Permanently delete a specific automation test session from LambdaTest by session ID.
Paramètres, retour & exemple (1)
ParamètressessionId· string · requis
The session ID to delete
Exemple d'appel{"name": "deleteSession", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - deleteUploadedApps≈ 131 tokens
Delete one or more uploaded apps from LambdaTest by their app IDs.
Paramètres, retour & exemple (1)
ParamètresappIds· array · requis
Array of app IDs to delete (at least one)
Exemple d'appel{"name": "deleteUploadedApps", "arguments": {"appIds": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - deleteUserFile≈ 150 tokens
Delete an uploaded user file by stored LambdaTest file path.
Paramètres, retour & exemple (2)
ParamètresfilePath· string · optionnel
Key of the stored user file, as uploadUserFile returns it (usually the file name)file_path· string · optionnel
Key of the stored user file, as uploadUserFile returns it (usually the file name)
Exemple d'appel{"name": "deleteUserFile", "arguments": {"filePath": "texte", "file_path": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - downloadJobArtifact≈ 236 tokens
Get an authenticated download URL (plus size/status metadata) for a specific HyperExecute job artifact. Requires artefactName (from getHyperExecuteJobArtifacts); optionally scope to a task with taskId. Returns a URL to fetch with your LambdaTest credentials rather than the raw file bytes.
Paramètres, retour & exemple (3)
ParamètresjobId· string · requis
The HyperExecute job ID whose artifact to downloadtaskId· string · optionnel
Optional: scope the artifact to a specific task IDartefactName· string · requis
Name of the artifact to download (as returned by getHyperExecuteJobArtifacts)
Exemple d'appel{"name": "downloadJobArtifact", "arguments": {"jobId": "texte", "artefactName": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - generateHyperExecuteYAML≈ 1929 tokens
Generates a HyperExecute YAML configuration for running tests on LambdaTest's HyperExecute platform. REQUIRED fields: project (language, framework) and testing (testDiscovery.command, testRunnerCommand) All other fields are OPTIONAL. Supports multiple languages and frameworks: - JavaScript/TypeScript: Playwright, Cypress, WebDriverIO, Puppeteer, Taiko - Python: Pytest, Behave, Robot Framework - Java: TestNG, JUnit, Cucumber - Ruby: RSpec, Capybara - C#: NUnit, xUnit, MSTest - Mobile (ONLY use appTesting for these): XCUI (iOS), Espresso (Android), Appium Features: - Smart framework defaults for common configurations - Input validation with security checks - Caching and artifact upload configuration - Git integration via sourcePayload - Mobile app testing support (via optional appTesting field) The appTesting field applies to mobile app testing only; web automation (Selenium, Playwright, Cypress, etc.) leaves it out.
Paramètres, retour & exemple (9)
Paramètressetup· object · optionnel
Setup configuration (optional)project· object · requis
Project configurationtesting· object · requis
Test configurationadvanced· object · optionnel
Advanced overrides (escape hatch for any HyperExecute field)jobLabel· array · optionnel
Labels for the jobartifacts· object · optionnel
Artifact configuration (optional)execution· object · optionnel
Execution settings (optional)appTesting· object · optionnel
Mobile app testing configuration (XCUI, Espresso or Appium). Web automation (Selenium, Playwright, Cypress, etc.) leaves it out.sourcePayload· object · optionnel
Git integration: fetches the test code from a remote Git repository. Only needed when the code is not already present locally; local code (the usual case) leaves it out.
Exemple d'appel{"name": "generateHyperExecuteYAML", "arguments": {"project": {}, "testing": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAccessibilityReport≈ 665 tokens
Runs an accessibility scan on the given URLs and returns the issues found. Pass urls to start a scan, or testId to re-read a scan that already ran; exactly one of the two. Results arrive in issueDetails: allIssues (most-severe-first, one page at a time), rules (name and reference link per rule id, listed once), pages (every scanned page with its score and issue count), failedRules (per-rule totals for the whole scan) and pagination. Each issue carries its own howToFix and criteria, measured for that element - two issues sharing a rule can have different causes and fixes. While pagination.nextOffset is not null the results are incomplete: call again with the testId from the response plus that offset, keeping the same filters, until it is null. Page with testId, never by passing urls again - that starts a new scan, costs another run, and can return a different set of issues whose offsets do not line up. a11yReportLink is the dashboard URL and needs a login; shareableLink is public and is only returned by the original scan.
Paramètres, retour & exemple (7)
Paramètresurls· array · optionnel
List of URLs to scan. Starts a new scan. Provide either urls or testId, not both.limit· number · optionnel
Maximum issues to return in this response (default 50, max 200).offset· number · optionnel
Index to start from within the filtered, severity-sorted issue list. Pass the nextOffset from a previous response, together with that response's testId, to page through results.testId· string · optionnel
Re-read an existing scan by its testId (as returned in a previous response) instead of running a new one. Use this to page through results with offset.pageUrl· string · optionnel
Only return issues found on this scanned page. Must exactly match one of the URLs in issueDetails.pages.severity· string · optionnel · critical | serious | moderate | minor
Only return issues of this impact level. Omit to get all severities.include_rules· boolean · optionnel
Return the full rule catalog (about 11 KB) instead of the default ruleCatalog summary of counts per category and disabled rule ids.
Exemple d'appel{"name": "getAccessibilityReport", "arguments": {"urls": [], "limit": 1, "offset": 1, "testId": "texte", "pageUrl": "texte", "severity": "critical"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAnalyticsData≈ 277 tokens
Summarises web automation test results in a date range: total tests, passed, failed, completed without a pass/fail mark, pass rate (passed over all tests, as the Insights page shows it), pass rate over tests marked passed or failed, average duration and distinct builds, grouped by status, browser, os, build, device or day. Computed from the automation test list (up to 5000 tests per call; the total is always exact).
Paramètres, retour & exemple (3)
ParamètrestoDate· string · optionnel
End date, YYYY-MM-DD. Defaults to today.groupBy· string · optionnel · status | browser | os | build | device | day
Dimension to group by. Defaults to status.fromDate· string · optionnel
Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
Exemple d'appel{"name": "getAnalyticsData", "arguments": {"toDate": "texte", "groupBy": "status", "fromDate": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAnalyticsErrors≈ 231 tokens
Summarises failed and errored web automation tests in a date range: counts by failure category and by status, and the failing tests themselves with build and environment. Failure categories exist only for about the last 7 days of tests; older failures are counted as uncategorised.
Paramètres, retour & exemple (3)
Paramètreslimit· number · optionnel
Maximum failing tests to list, 1 to 200. Defaults to 20.toDate· string · optionnel
End date, YYYY-MM-DD. Defaults to today.fromDate· string · optionnel
Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
Exemple d'appel{"name": "getAnalyticsErrors", "arguments": {"limit": 1, "toDate": "texte", "fromDate": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAutomationTestBrowserConsoleLogs≈ 184 tokens
Fetches Browser Console logs for a specific automation test. Note: Not available for mobile app automation tests.
Paramètres, retour & exemple (2)
ParamètrestestId· string · requis
The ID of the automation testplatform· string · requis · web | app
The platform type: "web" for browser automation, "app" for app automation (not supported)
Exemple d'appel{"name": "getAutomationTestBrowserConsoleLogs", "arguments": {"testId": "texte", "platform": "web"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAutomationTestCommandLogs≈ 234 tokens
Fetches command logs for a specific automation test
Paramètres, retour & exemple (4)
ParamètrestestId· string · requis
The ID of the automation testplatform· string · requis · web | app
The platform type: "web" for browser automation, "app" for app automationsessionId· string · optionnel
Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)pageNumber· number · optionnel
Page number to fetch (default: 1)
Exemple d'appel{"name": "getAutomationTestCommandLogs", "arguments": {"testId": "texte", "platform": "web"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAutomationTestDetails≈ 154 tokens
Fetches detailed information about an automation test by ID
Paramètres, retour & exemple (2)
ParamètrestestId· string · requis
The ID of the automation testplatform· string · requis · web | app
Optional: set to "app" to fetch details from the mobile API
Exemple d'appel{"name": "getAutomationTestDetails", "arguments": {"testId": "texte", "platform": "web"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAutomationTestNetworkLogs≈ 209 tokens
Fetches network logs for a specific automation test
Paramètres, retour & exemple (3)
ParamètrestestId· string · requis
The ID of the automation testplatform· string · requis · web | app
The platform type: "web" for browser automation, "app" for app automationsessionId· string · optionnel
Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)
Exemple d'appel{"name": "getAutomationTestNetworkLogs", "arguments": {"testId": "texte", "platform": "web"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getAutomationTestSeleniumLogs≈ 257 tokens
Fetches Selenium logs (web), Appium logs (mobile/Appium), or instrumentation logs (mobile/XCUI/Espresso) for a specific automation test. Automatically detects XCUI and Espresso tests and fetches the correct log type.
Paramètres, retour & exemple (3)
ParamètrestestId· string · requis
The ID of the automation test to fetch logs forplatform· string · requis · web | app
The platform type: "web" for Selenium logs, "app" for Appium/instrumentation logssessionId· string · optionnel
Required for app platform: the session_id of the app session, a UUID that listMobileSessions and getAutomationTestDetails return (not the test ID)
Exemple d'appel{"name": "getAutomationTestSeleniumLogs", "arguments": {"testId": "texte", "platform": "web"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getFlakyTests≈ 241 tokens
Lists tests that the insights engine marks as flaky (passing and failing intermittently) in a date range, with each test's flake rate, build and environment. Returns only flaky tests, plus how many tests were scanned. Flakiness is only computed for about the last 7 days of tests; the response says how many tests in the range had it.
Paramètres, retour & exemple (3)
Paramètreslimit· number · optionnel
Maximum flaky tests to return, 1 to 200. Defaults to 50.toDate· string · optionnel
End date, YYYY-MM-DD. Defaults to today.fromDate· string · optionnel
Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
Exemple d'appel{"name": "getFlakyTests", "arguments": {"limit": 1, "toDate": "texte", "fromDate": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteJobArtifacts≈ 148 tokens
Retrieve all artifacts or categorized errors for a HyperExecute job or task.
Paramètres, retour & exemple (2)
ParamètresjobId· string · requis
The HyperExecute job IDtaskId· string · optionnel
Optional: The HyperExecute task ID for categorized errors
Exemple d'appel{"name": "getHyperExecuteJobArtifacts", "arguments": {"jobId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteJobInfo≈ 124 tokens
Fetches and displays information about a HyperExecute job including status, test results, and progress.
Paramètres, retour & exemple (1)
ParamètresjobId· string · requis
The ID of the HyperExecute job
Exemple d'appel{"name": "getHyperExecuteJobInfo", "arguments": {"jobId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteJobLiveStream≈ 126 tokens
Stream live output from a running HyperExecute job. (UNDOCUMENTED - may change without notice)
Paramètres, retour & exemple (1)
ParamètresjobId· string · requis
The running job ID
Exemple d'appel{"name": "getHyperExecuteJobLiveStream", "arguments": {"jobId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteJobSessions≈ 144 tokens
Fetches and displays session information for a HyperExecute job.
Paramètres, retour & exemple (2)
ParamètresjobId· string · requis
The ID of the HyperExecute joblimit· number · optionnel
Maximum number of sessions to return (default: 10)
Exemple d'appel{"name": "getHyperExecuteJobSessions", "arguments": {"jobId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteStage≈ 171 tokens
Retrieve the stages of a HyperExecute task (cache/prerun/scenario/etc.). Pass a stageId to return just that one stage. Stages are keyed by their parent task, so taskId is required.
Paramètres, retour & exemple (2)
ParamètrestaskId· string · requis
The HyperExecute task ID whose stages to fetchstageId· string · optionnel
Optional: return only the stage with this ID
Exemple d'appel{"name": "getHyperExecuteStage", "arguments": {"taskId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteStageLogs≈ 119 tokens
Retrieve logs for a HyperExecute stage. (UNDOCUMENTED - may change without notice)
Paramètres, retour & exemple (1)
ParamètresstageId· string · requis
The stage ID
Exemple d'appel{"name": "getHyperExecuteStageLogs", "arguments": {"stageId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteStageTasks≈ 120 tokens
Retrieve tasks for a HyperExecute stage. (UNDOCUMENTED - may change without notice)
Paramètres, retour & exemple (1)
ParamètresstageId· string · requis
The stage ID
Exemple d'appel{"name": "getHyperExecuteStageTasks", "arguments": {"stageId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteTask≈ 117 tokens
Retrieve details for a HyperExecute task by task ID. (UNDOCUMENTED - may change without notice)
Paramètres, retour & exemple (1)
ParamètrestaskId· string · requis
The task ID
Exemple d'appel{"name": "getHyperExecuteTask", "arguments": {"taskId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getHyperExecuteTaskLogs≈ 117 tokens
Retrieve logs for a HyperExecute task. (UNDOCUMENTED - may change without notice)
Paramètres, retour & exemple (1)
ParamètrestaskId· string · requis
The task ID
Exemple d'appel{"name": "getHyperExecuteTaskLogs", "arguments": {"taskId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getJobArtifactDetail≈ 133 tokens
Get details for a specific artifact within a HyperExecute job.
Paramètres, retour & exemple (2)
ParamètresjobId· string · requis
The HyperExecute job IDartifactId· string · requis
The artifact ID
Exemple d'appel{"name": "getJobArtifactDetail", "arguments": {"jobId": "texte", "artifactId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getLiveSessionLogs≈ 172 tokens
Retrieve the request and response log of a test session, while it runs or after it ends. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
Paramètres, retour & exemple (1)
ParamètressessionId· string · requis
The web automation test ID (e.g. DA-WIN-...) or session ID
Exemple d'appel{"name": "getLiveSessionLogs", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getMobileCapabilityGenerator≈ 99 tokens
Retrieve capability generation data for mobile automation test configuration.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "getMobileCapabilityGenerator", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getMobileConcurrency≈ 97 tokens
Retrieve the current concurrency usage and limits for mobile automation (real device testing).
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "getMobileConcurrency", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getOrgConcurrency≈ 98 tokens
Retrieve the current concurrency usage and limits for the organization on web automation (Selenium/Cypress).
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "getOrgConcurrency", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getSessionScreenshots≈ 179 tokens
Retrieve command-by-command screenshots captured during a test session. Returns screenshot URLs for each step. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
Paramètres, retour & exemple (1)
ParamètressessionId· string · requis
The web automation test ID (e.g. DA-WIN-...) or session ID
Exemple d'appel{"name": "getSessionScreenshots", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getSessionV2CommandLogs≈ 184 tokens
Retrieve v2 command execution logs for a test session. Returns structured JSON with enhanced detail compared to v1 logs. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
Paramètres, retour & exemple (1)
ParamètressessionId· string · requis
The web automation test ID (e.g. DA-WIN-...) or session ID
Exemple d'appel{"name": "getSessionV2CommandLogs", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getSessionV2SeleniumLogs≈ 175 tokens
Retrieve v2 Selenium/WebDriver grid request and response logs for a test session. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
Paramètres, retour & exemple (1)
ParamètressessionId· string · requis
The web automation test ID (e.g. DA-WIN-...) or session ID
Exemple d'appel{"name": "getSessionV2SeleniumLogs", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getSessionVideo≈ 162 tokens
Retrieve the video recording URL for a completed test session. Web automation (Selenium, Playwright, Cypress) only: an app automation session returns not found; listMobileSessions carries the video and screenshot links of app sessions.
Paramètres, retour & exemple (1)
ParamètressessionId· string · requis
The web automation test ID (e.g. DA-WIN-...) or session ID
Exemple d'appel{"name": "getSessionVideo", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getSuiteOverview≈ 254 tokens
Gets comprehensive suite overview for a project including run counts, latest status, scores, schedule information, and active calls.
Paramètres, retour & exemple (1)
ParamètresprojectId· string · requis
The project ID to get suite overview for
Exemple d'appel{"name": "getSuiteOverview", "arguments": {"projectId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"suites": [], "project_id": "texte", "scheduled_runs": []}} - getSupportedPlatforms≈ 282 tokens
Lists the OS, browser and device combinations LambdaTest supports, to find valid os, browser and version values for a test configuration. With no filters it returns a compact summary: each desktop OS with its browsers (version count, newest and oldest) and resolutions, and each mobile platform with its device count and OS versions. Set os (and optionally browser) for the full version list, or os=ios / os=android for device names.
Paramètres, retour & exemple (3)
Paramètresos· string · optionnel
OS name to expand, matched case-insensitively as a substring, e.g. "Windows 11", "Sonoma", "android"type· string · optionnel · desktop | mobile
Only desktop OSes or only mobile platformsbrowser· string · optionnel
Browser to expand on desktop, e.g. "chrome", "firefox", "edge", "safari"
Exemple d'appel{"name": "getSupportedPlatforms", "arguments": {"os": "texte", "type": "desktop", "browser": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - getTestTrends≈ 192 tokens
Daily trend of web automation test results in a date range: for each day, total tests, passed, failed, completed without a pass/fail mark, pass rate (passed over all tests), pass rate over tests marked passed or failed, and average duration.
Paramètres, retour & exemple (2)
ParamètrestoDate· string · optionnel
End date, YYYY-MM-DD. Defaults to today.fromDate· string · optionnel
Start date, YYYY-MM-DD, within the last 59 days (older results are not served). Defaults to 30 days before toDate.
Exemple d'appel{"name": "getTestTrends", "arguments": {"toDate": "texte", "fromDate": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - listDevicesForTesting≈ 297 tokens
Lists the real devices available on LambdaTest for mobile app testing, 50 per page by default. Filter by region, OS, device name or OS version, and page with limit and offset. The text gives the total that matched.
Paramètres, retour & exemple (6)
Paramètresos· string · optionnel · android | ios
Operating system filterlimit· integer · optionnel
Devices per page, 1 to 200 (default 50)offset· integer · optionnel
Devices to skip (default 0)region· string · optionnel · us | ap | eu
Device region (default: us)deviceName· string · optionnel
Device name to match, case-insensitively as a substring, e.g. "Galaxy S24", "iPhone 15", "Pixel"platformVersion· string · optionnel
OS version to match, e.g. "14" (matches 14 and 14.x)
Exemple d'appel{"name": "listDevicesForTesting", "arguments": {"os": "android", "limit": 1, "offset": 1, "region": "us", "deviceName": "texte", "platformVersion": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - listHyperExecuteJobs≈ 213 tokens
List the account's HyperExecute jobs, newest first, with offset pagination and an optional status filter. The status filter looks at the 200 most recent jobs.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Maximum number of jobs to return, 1 to 200 (default 10)offset· integer · optionnel
Number of jobs to skip, after the status filter (default 0)status· string · optionnel
Only jobs with this status (e.g. completed, failed, running, skipped), among the 200 most recent
Exemple d'appel{"name": "listHyperExecuteJobs", "arguments": {"limit": 1, "offset": 1, "status": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - listMobileBuilds≈ 214 tokens
Lists mobile app automation builds, newest first, 10 per page by default. Page with limit and offset; the result gives the total the API reports. The API returns only builds from the last 90 days, so total can be higher than the builds you can page through.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
Rows per page, 1 to 100 (default 10)offset· integer · optionnel
Rows to skip (default 0)status· string · optionnel
Only builds with this status, e.g. completed, running, passed, failed
Exemple d'appel{"name": "listMobileBuilds", "arguments": {"limit": 1, "offset": 1, "status": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - listMobileSessions≈ 237 tokens
Lists mobile app automation sessions (tests), newest first, 10 per page by default, with their video, screenshot and log links. Page with limit and offset, or filter by buildId or status; the result gives the total the API reports.
Paramètres, retour & exemple (4)
Paramètreslimit· integer · optionnel
Rows per page, 1 to 100 (default 10)offset· integer · optionnel
Rows to skip (default 0)status· string · optionnel
Only sessions with this status, e.g. passed, failed, completed, errorbuildId· string · optionnel
Only sessions of this build (build_id from listMobileBuilds)
Exemple d'appel{"name": "listMobileSessions", "arguments": {"limit": 1, "offset": 1, "status": "texte", "buildId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - listTunnels≈ 111 tokens
Retrieve all active LambdaTest tunnel connections for the account. Useful for checking which tunnels are running before starting a new one or debugging local testing connectivity.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "listTunnels", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - listUploadedApps≈ 193 tokens
Retrieve all apps uploaded to LambdaTest for mobile testing. Use type=android/ios for real devices, emulator/simulator for virtual devices.
Paramètres, retour & exemple (2)
Paramètrestype· string · optionnel · android | ios | emulator | simulator
App type: android/ios for real devices, emulator/simulator for virtuallevel· string · optionnel · user | team
Scope: user (default, apps you uploaded) or team (apps across your organization; sent to the API as level=org)
Exemple d'appel{"name": "listUploadedApps", "arguments": {"type": "android", "level": "user"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - postSessionExceptions≈ 263 tokens
Upload exception/error logs from the client machine for a test session, by session ID. Use this to attach assertion failures or unexpected errors to a session. The result reads the test's exceptions back to confirm they were stored. The automation dashboard may not show exceptions uploaded this way after the test ended.
Paramètres, retour & exemple (2)
Paramètresdata· object · requis
The exceptions to attach: {"exception": ["first message", "second message"]}sessionId· string · requis
The session ID
Exemple d'appel{"name": "postSessionExceptions", "arguments": {"data": {}, "sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - postTestExceptions≈ 239 tokens
Upload exception logs for a specific test (by test ID) rather than by session ID. The result reads the test's exceptions back to confirm they were stored. The automation dashboard may not show exceptions uploaded this way after the test ended.
Paramètres, retour & exemple (2)
Paramètresdata· object · requis
The exceptions to attach: {"exception": ["first message", "second message"]}testId· string · requis
The test ID
Exemple d'appel{"name": "postTestExceptions", "arguments": {"data": {}, "testId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - smartui_baseline_manage≈ 335 tokens
Merge SmartUI baselines across branches or builds (to read baseline settings, use smartui_project_query with action=get). merge_branch/merge_build resolve source and target names to builds, merge them, then poll the merged build and report its real terminal status — a merge that lands in error or with zero screenshots is returned as a tool error, not as success. Merging permanently changes baseline state: the merged build takes the baseline flag, so a failed merge leaves the baseline on an empty build.
Paramètres, retour & exemple (4)
Paramètresaction· string · requis · merge_branch | merge_build
merge_branch merges one branch baseline into another; merge_build merges one build into anothersource· string · optionnel
Source branch (merge_branch) or build name (merge_build) to merge FROMtarget· string · optionnel
Target branch (merge_branch) or build name (merge_build) to merge INTOproject_id· string · requis
Project id (required)
Exemple d'appel{"name": "smartui_baseline_manage", "arguments": {"action": "merge_branch", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - smartui_build_query≈ 408 tokens
List SmartUI builds in a project, get one build, or get the CI gate verdict for a build. Use action=gate in pipelines: it returns verdict (passed|failed|pending_approval|running|error), totals (including missing screenshots the baseline has), blocking_comparison_ids, and blocking[] with per-item detail. verdict=failed covers rejections AND builds that dropped baseline screenshots. Read-only.
Paramètres, retour & exemple (8)
Paramètrespage· number · optionnel
Page number (list only, 1-based)limit· number · optionnel
Page size (list only, default 50, max 200)action· string · requis · list | get | gate
list builds, get one build, or gate (CI verdict)branch· string · optionnel
Filter builds by branch (list only)build_id· string · optionnel
Build id — required for get/gate (or use build_name)build_name· string · optionnel
Build name. get/gate: exact name, an alternative to build_id. list: case-insensitive substring filter, applied client-side to the newest 200 builds (upstream has no name filter).project_id· string · requis
Project id (required)build_status· string · optionnel
Substring filter on build status (list only), e.g. "pending-approval"
Exemple d'appel{"name": "smartui_build_query", "arguments": {"action": "list", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - smartui_comparison_analyze≈ 394 tokens
Analyze one SmartUI comparison through a lens: consolidated (default), pixel, or dom. Returns the comparison data (mismatch %, verdict, correctly-labelled asset URLs) plus, for lens=dom, a real DOM byte delta when the artefact is served — no local filesystem needed. consolidated and pixel report upstream numbers and point at the assets; they do not run their own image analysis. lens=dom degrades to a structured error when DOM artefacts are not served. Read-only.
Paramètres, retour & exemple (3)
Paramètreslens· string · optionnel · consolidated | pixel | dom
Analysis lens (default consolidated). layout and perceptual were retired — they returned the consolidated payload unchanged.comparison_id· string · requis
Comparison id (required) — from smartui_comparison_queryinclude_assets· string · optionnel · urls | inline
urls (default) returns asset URLs only. inline additionally attaches the screenshots themselves as image blocks — compared only for lens=pixel, baseline+current+compared for consolidated, none for lens=dom. Images over 1.5 MB (or past 2.25 MB in total) are skipped and listed with the reason; their URLs stay in the result. Use inline when you cannot fetch URLs.
Exemple d'appel{"name": "smartui_comparison_analyze", "arguments": {"comparison_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - smartui_comparison_query≈ 350 tokens
List all comparisons in a SmartUI build (each row returns comparison_id AND ss_id), or get one comparison's detail (mismatch %, status, correctly-labelled baseline/current/compared asset URLs). This is how you obtain a comparison_id — you never need the dashboard. Read-only.
Paramètres, retour & exemple (8)
Paramètrespage· number · optionnel
Page number (list only, 1-based)limit· number · optionnel
Page size (list only, default 50, max 200)action· string · requis · list | get
list comparisons in a build, or get one by comparison_idstatus· string · optionnel
Filter by status (list only), e.g. "changes_found", "approved"build_id· string · optionnel
Build id — required for action=listproject_id· string · optionnel
Project id — required for action=listmin_mismatch· number · optionnel
Only comparisons with mismatch_percentage >= this (list only)comparison_id· string · optionnel
Comparison id — required for action=get
Exemple d'appel{"name": "smartui_comparison_query", "arguments": {"action": "list"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - smartui_project_query≈ 271 tokens
List SmartUI projects, or get one project with its settings — action=get returns baseline_branch, approvers[], smart_baseline, auto_approval_branch, overwrite_screenshot and project_category alongside platform and project_type. Start here when you do not have a project_id. Read-only.
Paramètres, retour & exemple (5)
Paramètrespage· number · optionnel
Page number (list only, 1-based)limit· number · optionnel
Page size (list only, default 50, max 200)action· string · requis · list | get
list all projects, or get one by project_idsearch· string · optionnel
Case-insensitive substring filter on project name (list only)project_id· string · optionnel
Project id — required for action=get
Exemple d'appel{"name": "smartui_project_query", "arguments": {"action": "list"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - smartui_screenshot_review≈ 394 tokens
Approve or reject SmartUI comparisons — individually (comparison_ids or ss_ids), or for a whole build (all_matching:{status}). Ids are validated against the build before writing, and results are verified by re-reading status, so the response reports real per-item updated[]/failed[] and whether the baseline was promoted. Approving comparisons on the baseline branch can promote the build to baseline.
Paramètres, retour & exemple (6)
Paramètresaction· string · requis · approve | reject
approve or reject the selected comparisonsss_ids· array · optionnel
Screenshot-variant ids to review directlybuild_id· string · requis
Build id the comparisons belong to (required)project_id· string · requis
Project id (required)all_matching· object · optionnel
Review every comparison in the build matching a statuscomparison_ids· array · optionnel
Comparison ids to review (resolved to ss_ids server-side)
Exemple d'appel{"name": "smartui_screenshot_review", "arguments": {"action": "approve", "build_id": "texte", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - smartui_screenshot_upload≈ 446 tokens
Upload screenshots to a SmartUI project as a new build, from local file_paths or from source_urls (fetched server-side, so it works without a client filesystem). Pass project_id to auto-resolve the project token. Set mark_baseline=true to seed a baseline. Returns build_id; follow with smartui_build_query(action=gate).
Paramètres, retour & exemple (7)
Paramètresaction· string · requis · images
What to upload (currently images)build_name· string · optionnel
Name for this build (optional)file_paths· array · optionnel
Absolute local image paths (.png/.jpg/.jpeg). Only usable when the MCP server runs locally over stdio — the hosted server cannot see your filesystem; use source_urls there.project_id· string · optionnel
Project id — preferred; the projectToken is resolved automaticallysource_urls· array · optionnel
Public http/https image URLs, fetched server-side (max 20). Works in hosted mode.mark_baseline· boolean · optionnel
Mark this build as the baselinescreenshot_name· string · optionnel
Name this screenshot (binds it to that baseline) instead of using the file/URL name. Sent exactly as given, with no extension added, so pass the baseline name as it appears in SmartUI (SDK and CLI captures have no extension). Only valid when uploading exactly one image.
Exemple d'appel{"name": "smartui_screenshot_upload", "arguments": {"action": "images"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - stopBuild≈ 124 tokens
Stops every running test in a LambdaTest web automation build. Running sessions end immediately.
Paramètres, retour & exemple (1)
ParamètresbuildId· number · requis
ID of the build to stop
Exemple d'appel{"name": "stopBuild", "arguments": {"buildId": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - stopSession≈ 104 tokens
Stop an active running test session on LambdaTest.
Paramètres, retour & exemple (1)
ParamètressessionId· string · requis
The session ID to stop
Exemple d'appel{"name": "stopSession", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - stopTunnel≈ 120 tokens
Terminate a specific active tunnel connection by tunnel ID. Use this to clean up tunnels that are no longer needed.
Paramètres, retour & exemple (1)
ParamètrestunnelId· string · requis
The ID of the tunnel to stop
Exemple d'appel{"name": "stopTunnel", "arguments": {"tunnelId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_create_folder≈ 301 tokens
Create a folder — in a project's Test Cases tree (default) or Test Runs tree (pass project_id), or in the organization-level Modules tree (no project_id needed; module folders are shared across projects). Optionally nest it under an existing parent folder to build folder trees. Deleting folders is not available through this connection.
Paramètres, retour & exemple (5)
Paramètresname· string · requis
Folder nametree· string · optionnel · test-cases | test-runs | modules
Which folder tree to create in (default test-cases). "modules" is organization-level.project_id· string · optionnel
Project ID (ULID) — required for the test-cases and test-runs trees; not used for modulesdescription· string · optionnel
Optional descriptionparent_folder_id· string · optionnel
Nest under this existing folder (ULID); omit for top level
Exemple d'appel{"name": "tm_create_folder", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_create_milestone≈ 282 tokens
Create a milestone in a project (status: Open), optionally with description, start/end dates, tags, and existing runs attached.
Paramètres, retour & exemple (8)
Paramètrestags· array · optionnel
Labelsowner· string · optionnel
Milestone owner: an organization member (email, username, or user id). Omit for no owner.title· string · requis
Milestone titleend_at· string · optionnel
End date (YYYY-MM-DD)start_at· string · optionnel
Start date (YYYY-MM-DD)project_id· string · requis
Project ID (ULID)description· string · optionnel
What this milestone coverstest_run_ids· array · optionnel
Existing run ids to attach
Exemple d'appel{"name": "tm_create_milestone", "arguments": {"title": "texte", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_create_project≈ 168 tokens
Create a new Test Manager project. Project & Org Instructions (Memory Layer) stay managed in the UI. Deleting projects is not available through this connection.
Paramètres, retour & exemple (3)
Paramètresname· string · requis
Project nametags· array · optionnel
Labelsdescription· string · optionnel
What the project covers
Exemple d'appel{"name": "tm_create_project", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_create_test_case≈ 546 tokens
Create a single test case in a project folder, with optional steps and references to existing step Modules (module steps are included; the Module itself is unchanged). For creating many cases from a requirement, prefer tm_generate_test_cases.
Paramètres, retour & exemple (13)
Paramètrestags· array · optionnel
Labelstype· string · optionnel
e.g. Functional, Regression, Smoke & Sanitytitle· string · requis
Test case titlestatus· string · optionnel
e.g. Live, Unverified, Ready (default per project settings)priority· string · optionnel
Lowest, Low, Medium, High or Highestfolder_id· string · optionnel
Folder to file the case intomodule_ids· array · optionnel
Existing step Module ids to include (appended as module steps after test_steps)project_id· string · requis
Project ID (ULID)test_steps· array · optionnel
Ordered stepsdescription· string · optionnel
What the case verifiespreconditions· string · optionnel
Setup required before the stepsestimated_time· number · optionnel
Estimated execution time in minutesautomation_status· string · optionnel
Automated, Not Automated or To Be Automated
Exemple d'appel{"name": "tm_create_test_case", "arguments": {"title": "texte", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_create_test_run≈ 636 tokens
Create a test run from chosen test cases — manual (default) or KaneAI (run_type: "kaneai"). Each included test case becomes a TEST RUN INSTANCE — the executable copy of that test inside the run, which carries its own status, remarks and exactly one Configuration. The cases must match the run type: KaneAI runs only take KaneAI-authored cases with completed code generation; manual runs only take manual cases. Optionally attach existing milestones, file into a run folder, and apply a Configuration to all instances (KaneAI configurations must be compatible with each case's platform — web/mobile-app/mobile-browser and iOS/Android).
Paramètres, retour & exemple (12)
Paramètrestags· array · optionnel
Labelstitle· string · requis
Run titleassignee· string · optionnel
Assign every created instance to this organization member: email, username, or user id. Omit to leave the instances unassigned.run_type· string · optionnel · manual | kaneai
Run type (default manual). "kaneai" creates a KaneAI run: only KaneAI-authored test cases can be included, and configurations must be kane-supported and platform-compatible.folder_id· string · optionnel
Test-run folder to file the run intoobjective· string · optionnel
What this run verifiesproject_id· string · requis
Project ID (ULID)is_sequential· boolean · optionnel
KaneAI runs only: execute the instances sequentially (default false).milestone_ids· array · optionnel
Existing milestone ids to attach the run totest_case_ids· array · optionnel
Test case ids to includeconfiguration_id· number · optionnel
Apply ONE Configuration to every included test case (the configuration's top-level id from tm_list_configurations)configuration_ids· array · optionnel
Apply MULTIPLE Configurations: each included test case gets one test run instance per configuration (case × configuration), like the UI's Add Configuration checkboxes
Exemple d'appel{"name": "tm_create_test_run", "arguments": {"title": "texte", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_generate_test_cases≈ 770 tokens
Generate structured test cases from a requirement or prompt using the Test Manager AI generator (applies the project's Memory Layer — Project & Org Instructions — automatically) and file them into the chosen folder. Requirement documents, specs, spreadsheets or screenshots can be attached via files to ground the generation. Volume = test_scenario_limit × per_scenario_test_cases_limit, capped at 50 per call. By default all generated cases are saved into the folder (one sub-folder per scenario); pass auto_save=false to review before saving. The call returns FAST with a request_id (and a browser progress URL) — generation takes ~30-90s in the background; call this tool again with just request_id to check progress, fetch results, or save. Note: consumes AI generation credits.
Paramètres, retour & exemple (9)
Paramètresfiles· array · optionnel
Optional reference files to ground the generation (requirement docs, specs, data sheets, screenshots). Each item carries the file name and its raw bytes base64-encoded in content_base64. Supported: .pdf, .docx, .txt, .csv, .xlsx, .json, .xml, .jpg, .jpeg, .png, .gif, .bmp, .webp; max 5 files, 10 MB each. Large files are better uploaded in the Test Manager UI, since the base64 content travels in the request. Only used when starting a new generation.prompt· string · optionnel
The requirement / instructions to generate test cases from. Required when starting a new generation.jira_ids· array · optionnel
Optional Jira issue keys to use as requirement contextauto_save· boolean · optionnel
Save all generated cases into the folder automatically (default true for a NEW generation). Set false to review first — that choice persists across request_id polls (a bare poll never saves it); to save after review, call again with request_id AND auto_save=true.folder_id· string · optionnel
Folder to file generated cases into. Required when starting a new generation.project_id· string · optionnel
Project ID (ULID). Required when starting a new generation.request_id· number · optionnel
Resume/act on an earlier generation: check progress, fetch results, or save them.test_scenario_limit· number · optionnel
Max scenarios to generate (default 3)per_scenario_test_cases_limit· number · optionnel
Max test cases per scenario (default 3)
Exemple d'appel{"name": "tm_generate_test_cases", "arguments": {"files": [], "prompt": "texte", "jira_ids": [], "auto_save": true, "folder_id": "texte", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_get_coverage_summary≈ 308 tokens
Test coverage for a project, overall and per folder, computed live from the project's test cases (matches the Test Cases screen). Also answers requirement and traceability coverage: pass jira_id (any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug) to get that item's test coverage (the test cases linked to it and how many are automated; zero linked cases means uncovered). For a set of requirements, call once per Jira key. A scope with no test cases returns all zeros; a Jira key that does not exist in the connected Jira returns an error.
Paramètres, retour & exemple (3)
Paramètresjira_id· string · optionnel
Optional Jira issue key (e.g. TE-123) — scope coverage to the test cases linked to this requirement / user story / epic / ticket (traceability coverage)folder_id· string · optionnel
Optional folder scopeproject_id· string · requis
Project ID (ULID)
Exemple d'appel{"name": "tm_get_coverage_summary", "arguments": {"project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_get_milestone≈ 159 tokens
Pass milestone_id to get one milestone's detail and live completion progress. Otherwise pass project_id to list the project's milestones.
Paramètres, retour & exemple (2)
Paramètresproject_id· string · optionnel
Project ID (ULID). Required when milestone_id is not given.milestone_id· string · optionnel
Milestone ID (ULID). When given, returns detail + progress.
Exemple d'appel{"name": "tm_get_milestone", "arguments": {"project_id": "texte", "milestone_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_get_test_cases≈ 416 tokens
Find test cases in a project by filters (folder, priority, automation status, type, tags) and/or search (matches test case ID like TC-123, or title; minimum 3 characters) — returns summaries. Filters combine (AND). Pass case_id instead to get one case's full detail (steps, BDD scenarios, field values).
Paramètres, retour & exemple (10)
Paramètrespage· number · optionnel
Page number (1-based)tags· array · optionnel
Filter by tagstype· string · optionnel
Filter by test type (e.g. Functional, Regression, Smoke & Sanity)limit· number · optionnel
Max results per pagesearch· string · optionnel
Full-text keyword (min 3 chars)case_id· string · optionnel
Test case ID (ULID). When given, returns that case's full detail and all other filters are ignored.priority· string · optionnel
Filter by priority (e.g. Lowest, Low, Medium, High, Highest). A value outside the project's priority list is rejected with the valid values.folder_id· string · optionnel
Only cases in this folderproject_id· string · optionnel
Project ID (ULID). Required unless case_id is given.automation_status· string · optionnel
Filter by automation status (e.g. Automated, Not Automated, To Be Automated)
Exemple d'appel{"name": "tm_get_test_cases", "arguments": {"page": 1, "tags": [], "type": "texte", "limit": 1, "search": "texte", "case_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_get_test_runs≈ 380 tokens
Pass run_id to get one test run's detail plus its result summary (instance counts by status — passed / failed / skipped / not started / in progress — and pass rate). Otherwise pass project_id to list runs with optional filters. Every returned run carries run_type ("kaneai" or "manual") identifying KaneAI runs — the backend stores KaneAI runs with type "Manual" (result-entry mode), so use run_type, not type, to tell them apart.
Paramètres, retour & exemple (8)
Paramètrespage· number · optionnel
Page number (1-based)limit· number · optionnel
Max results per pagerun_id· string · optionnel
Test run ID (ULID). When given, returns detail + result summary.search· string · optionnel
Search runs by titlestatus· string · optionnel
Filter: Not Started, In Progress, Passed, Failed, Skippedrun_type· string · optionnel
Filter: "kaneai" (KaneAI runs), "manual" (human result-entry runs, KaneAI excluded), or "automation" (framework-uploaded runs). Buckets are disjoint.folder_id· string · optionnel
Only runs in this folderproject_id· string · optionnel
Project ID (ULID). Required when run_id is not given.
Exemple d'appel{"name": "tm_get_test_runs", "arguments": {"page": 1, "limit": 1, "run_id": "texte", "search": "texte", "status": "texte", "run_type": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_link_ado_issue≈ 304 tokens
Link a test case, test run, or a run result (instance) to an Azure DevOps work item (requirement / user story / bug) by its URL — linked test cases are what give the work item its test coverage and traceability. Requires the Azure DevOps integration to be set up for the organization — otherwise a clear "set up Azure DevOps first" message is returned.
Paramètres, retour & exemple (4)
Paramètresentity_id· string · requis
Id of the case (ULID), run (ULID) or instance (number as string)project_id· string · requis
Project ID (ULID) the entity belongs toentity_type· string · requis · test_case | test_run | test_run_instance
What to linkwork_item_url· string · requis
The Azure DevOps work item URL, e.g. https://dev.azure.com/<organization>/<project>/_workitems/edit/165
Exemple d'appel{"name": "tm_link_ado_issue", "arguments": {"entity_id": "texte", "project_id": "texte", "entity_type": "test_case", "work_item_url": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_link_jira_issue≈ 252 tokens
Link a test case, test run, or a run result (instance) to a Jira issue (requirement / user story / epic / bug) — linked test cases are what give the issue its test coverage and traceability. Linking a result also links its case and run. Requires the Jira integration to be set up for the organization — otherwise a clear "set up Jira first" message is returned.
Paramètres, retour & exemple (3)
Paramètresissue_id· string · requis
Jira issue key, e.g. TE-123entity_id· string · requis
Id of the case (ULID), run (ULID) or instance (number as string)entity_type· string · requis · test_case | test_run | test_run_instance
What to link
Exemple d'appel{"name": "tm_link_jira_issue", "arguments": {"issue_id": "texte", "entity_id": "texte", "entity_type": "test_case"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_list_configurations≈ 315 tokens
List saved run Configurations (reusable platform / browser / OS / device setups). To apply one to a run, pass the configuration's TOP-LEVEL id to tm_create_test_run or tm_update_test_run as configuration_id (NOT the nested environments[].environment_id). Pass run_type to see only the configurations usable for that run type (kaneai vs manual). Each test instance carries exactly one configuration. Configurations are created by humans in the Test Manager UI. They are organization-level (shared by every project), so there is no project filter. Results are paged: the response says how many exist in total; page through them or raise limit to see all.
Paramètres, retour & exemple (3)
Paramètrespage· number · optionnel
Page number (1-based)limit· number · optionnel
Max results per page (default 10)run_type· string · optionnel · manual | kaneai
Only configurations supporting this run type (kane-supported vs manual-supported)
Exemple d'appel{"name": "tm_list_configurations", "arguments": {"page": 1, "limit": 1, "run_type": "manual"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_list_folders≈ 234 tokens
Get a folder tree. Test Manager keeps three folder types: Test Cases and Test Runs folders (per project — pass project_id) and Modules folders (organization-level, since modules are shared across projects — no project_id needed). Pick with the tree parameter (default: test-cases). New test-case/test-run folders can be created with tm_create_folder.
Paramètres, retour & exemple (2)
Paramètrestree· string · optionnel · test-cases | test-runs | modules
Which folder tree to return (default test-cases). "modules" is organization-level.project_id· string · optionnel
Project ID (ULID) — required for the test-cases and test-runs trees; not used for modules
Exemple d'appel{"name": "tm_list_folders", "arguments": {"tree": "test-cases", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_list_modules≈ 264 tokens
List the organization's reusable step Modules (modules are org-level, shared across projects — the same list as the Modules page). Supports name search and pagination. Reference a module by id when creating or editing a test case to include its steps (the Module itself is never changed).
Paramètres, retour & exemple (5)
Paramètrespage· number · optionnel
Page number (1-based)limit· number · optionnel
Max results per page (default 100)search· string · optionnel
Filter modules by name keywordfolder_id· string · optionnel
Only modules in this Modules folder (folder ids from tm_list_folders with tree="modules")include_subfolders· boolean · optionnel
With folder_id: also include modules from its subfolders
Exemple d'appel{"name": "tm_list_modules", "arguments": {"page": 1, "limit": 1, "search": "texte", "folder_id": "texte", "include_subfolders": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_list_projects≈ 159 tokens
List all Test Manager projects the authenticated user is allowed to see. Supports keyword search and pagination.
Paramètres, retour & exemple (3)
Paramètrespage· number · optionnel
Page number (1-based)limit· number · optionnel
Max results per page (default 25)search· string · optionnel
Filter projects by name keyword
Exemple d'appel{"name": "tm_list_projects", "arguments": {"page": 1, "limit": 1, "search": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_record_test_results≈ 682 tokens
Record execution results on a MANUAL run's TEST RUN INSTANCES (the per-run copies of each test case) — max 500 per request, all-or-nothing (larger requests are rejected with nothing recorded). Manual runs only: KaneAI run results are recorded by KaneAI executions, so manual entry on a KaneAI run is rejected. Target an instance by instance_id, or just pass test_case_id and the instance is resolved automatically. Valid statuses: Passed, Failed, Skipped, Not Started (terminal — run-level "In Progress" is set via tm_update_test_run). Re-recording a step status replaces its result: an omitted step remark is cleared; response echoes per-step outcomes. Optional remarks and assignee per result, and per-step results via steps[] (mark individual test steps / BDD scenario rows Passed/Failed/Skipped with remarks, like the UI's per-step Mark Status). Note: this sets INSTANCE statuses; the run's overall status is set separately via tm_update_test_run.
Paramètres, retour & exemple (2)
Paramètresrun_id· string · requis
Test run ID (ULID)results· array · requis
Results to record (max 500)
Exemple d'appel{"name": "tm_record_test_results", "arguments": {"run_id": "texte", "results": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_update_folder≈ 329 tokens
Rename a folder, change its description, or move it under a different parent folder. Works on all three folder types: per-project Test Cases (default) and Test Runs trees, and the organization-level Modules tree. Moves of test-cases/test-runs folders require project_id; module folders need none.
Paramètres, retour & exemple (6)
Paramètresname· string · optionnel
New nametree· string · optionnel · test-cases | test-runs | modules
Which folder tree the folder belongs to (default test-cases). "modules" is organization-level.folder_id· string · requis
Folder ID (ULID)project_id· string · optionnel
Project ID (ULID) — required when moving a test-cases or test-runs folder; not used for modulesdescription· string · optionnel
New descriptionparent_folder_id· string · optionnel
Move under this folder (ULID), or pass "root" to make it a top-level folder; cannot be the folder itself or one of its descendants
Exemple d'appel{"name": "tm_update_folder", "arguments": {"folder_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_update_milestone≈ 346 tokens
Update a milestone — title, description, dates, tags — or change its status (e.g. mark it Completed). Deleting milestones is not available through this connection.
Paramètres, retour & exemple (9)
Paramètrestags· array · optionnel
Replace tagsowner· string · optionnel
Change the milestone Owner — an organization member (email, username, or user id).title· string · optionnel
New titleend_at· string · optionnel
End date (YYYY-MM-DD)status· string · optionnel
New status: Open (reopen) or Complete — the UI's two milestone states. "Active" and "Completed" are accepted as aliases and normalized to Open/Complete (any other stored value hides the milestone from the UI lists).start_at· string · optionnel
Start date (YYYY-MM-DD)project_id· string · requis
Project ID (ULID)description· string · optionnel
New descriptionmilestone_id· string · requis
Milestone ID (ULID)
Exemple d'appel{"name": "tm_update_milestone", "arguments": {"project_id": "texte", "milestone_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_update_project≈ 182 tokens
Update a project's name, description or tags (fields are merged — only what you pass changes). Project & Org Instructions stay managed in the UI.
Paramètres, retour & exemple (4)
Paramètresname· string · optionnel
New nametags· array · optionnel
Replace tagsproject_id· string · requis
Project ID (ULID)description· string · optionnel
New description
Exemple d'appel{"name": "tm_update_project", "arguments": {"project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_update_test_case≈ 534 tokens
Edit an existing test case (fields are merged — only what you pass changes). test_steps, when given, REPLACE the case's steps; module_ids append module reference steps. Deleting test cases is not available through this connection.
Paramètres, retour & exemple (14)
Paramètrestags· array · optionnel
Replace tagstype· string · optionnel
Test typetitle· string · optionnel
New titlestatus· string · optionnel
e.g. Live, Archived, Faulty, Readycase_id· string · requis
Test case ID (ULID)priority· string · optionnel
Lowest, Low, Medium, High or Highestfolder_id· string · optionnel
Move to this foldermodule_ids· array · optionnel
Existing step Module ids to append as module stepsproject_id· string · requis
Project ID (ULID)test_steps· array · optionnel
Replacement steps (omit to keep current steps)description· string · optionnel
New descriptionpreconditions· string · optionnel
New preconditionsestimated_time· number · optionnel
Estimated minutesautomation_status· string · optionnel
Automated, Not Automated or To Be Automated
Exemple d'appel{"name": "tm_update_test_case", "arguments": {"case_id": "texte", "project_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - tm_update_test_run≈ 684 tokens
Update an open test run — overall status (Passed / Failed / Skipped / In Progress), title, objective, milestones, folder, add test cases (each added case becomes a new test run instance; cases must match the run's type — KaneAI or manual), apply a Configuration to the run's instances (configuration_id; on KaneAI runs it must be kane-supported and platform-compatible with the targeted cases), toggle sequential execution (KaneAI runs), or archive it. Only open (active) runs can be updated; a closed/archived run returns a clear message. Adding cases/milestones appends, never replaces.
Paramètres, retour & exemple (13)
Paramètrestitle· string · optionnel
New titlerun_id· string · requis
Test run ID (ULID)status· string · optionnel · Passed | Failed | Skipped | In Progress
Set the run's OVERALL status (independent of per-instance results). Manual runs only — KaneAI run status is managed by KaneAI executions.archive· boolean · optionnel
Archive (close) the runassignee· string · optionnel
Assign the run's instances to this organization member: email, username, or user id ("none" clears). Scope with apply_to_test_case_ids. Omit to keep the current assignee.folder_id· string · optionnel
Move to this run folderobjective· string · optionnel
New objectiveis_sequential· boolean · optionnel
KaneAI runs only: execute the instances sequentially.milestone_ids· array · optionnel
Milestone ids to attach (appended)configuration_id· number · optionnel
Set ONE Configuration on the run's instances (the configuration's top-level id from tm_list_configurations; each instance carries exactly one configuration)add_test_case_ids· array · optionnel
Test case ids to add to the run (appended)configuration_ids· array · optionnel
APPEND multiple Configurations: each targeted test case gets an additional instance per configuration (case × configuration, like the UI); existing configured instances are untouchedapply_to_test_case_ids· array · optionnel
With configuration_id or configuration_ids: only apply to these test cases (default: all instances in the run)
Exemple d'appel{"name": "tm_update_test_run", "arguments": {"run_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - triggerSuiteRun≈ 224 tokens
Triggers a phone call test run for a specific suite. This will initiate phone calls for all scenarios configured in the suite.
Paramètres, retour & exemple (2)
ParamètresprojectId· string · requis
The project ID that contains the suitesuiteName· string · requis
The name of the suite to trigger
Exemple d'appel{"name": "triggerSuiteRun", "arguments": {"projectId": "texte", "suiteName": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": {}, "message": "texte", "success": true}} - updateBuild≈ 139 tokens
Renames a LambdaTest web automation build. Overwrites the current build name.
Paramètres, retour & exemple (2)
Paramètresname· string · requis
New build namebuildId· number · requis
ID of the build to rename
Exemple d'appel{"name": "updateBuild", "arguments": {"name": "texte", "buildId": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - updateSession≈ 178 tokens
Update the name or pass/fail status of a test session. Use status_ind to mark tests as passed, failed, error, or skipped from your test framework.
Paramètres, retour & exemple (3)
Paramètresname· string · optionnel
New name for the sessionsessionId· string · requis
The session ID to updatestatus_ind· string · optionnel · passed | failed | error | skipped
Test result status
Exemple d'appel{"name": "updateSession", "arguments": {"sessionId": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - uploadAppVirtualDevice≈ 262 tokens
Upload an app (APK for emulator, IPA for simulator) to LambdaTest for virtual device (emulator/simulator) testing.
Paramètres, retour & exemple (6)
Paramètresname· string · requis
Name for the uploaded appappUrl· string · optionnel
Public URL of the app to upload (alternative to filePath)storage· string · optionnel · file | url
Storage method (default: url when appUrl provided)filePath· string · optionnel
Absolute local path to the app file (APK or IPA)custom_id· string · optionnel
Custom identifier for the appvisibility· string · optionnel · individual | team
Access level (default: individual)
Exemple d'appel{"name": "uploadAppVirtualDevice", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - upload_app≈ 360 tokens
Uploads an app to LambdaTest for mobile testing and displays upload status.
Paramètres, retour & exemple (5)
Paramètresname· string · requis
Name for the uploaded appappUrl· string · optionnel
URL of the app to upload. Provide this OR appFilePath (exactly one is required).customId· string · optionnel
Custom ID for the app (optional)visibility· string · optionnel · individual | team | organization
Visibility setting (optional, default: individual)appFilePath· string · optionnel
Absolute path to the app file (APK, IPA, etc.). Provide this OR appUrl (exactly one is required).
Exemple d'appel{"name": "upload_app", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"appId": "texte", "error": "texte", "appUrl": "texte", "message": "texte", "success": true}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».