Create a new JMeter test plan. Returns the planId and the id of its root TestPlan node, which you'll use as parentId for the first thread group.

List all test plans in the workspace.

Get the full element tree of a test plan, including every node's id (needed as parentId for add_* tools) and type.

Add a Thread Group (virtual users) under the given parent node (usually the TestPlan root).

Add an HTTP Request sampler under the given parent node (usually a Thread Group).

Add a JSON Extractor post-processor under an HTTP sampler, to save a value from the JSON response into a variable.

Add an HTTP Header Manager under an HTTP sampler (or a Thread Group, to apply to every sampler in it).

Add a Response Assertion under an HTTP sampler, to fail the sample if the response doesn't match.

Add an Aggregate Report listener under the given parent (Thread Group or TestPlan). Its output is what get_execution_report reads after a run.

Add a Summary Report listener under the given parent (Thread Group or TestPlan). Its output is what get_execution_report reads after a run.

Start running a test plan with JMeter in non-GUI mode. Returns immediately with an executionId; the run continues in the background. Poll get_execution_status to know when it's done, then call get_execution_report to read the results.

Check the status of a test run started with execute_test_plan (running/completed/failed), plus the tail of its log.

Stop a running test execution (sends SIGTERM to the JMeter process).

Read and aggregate the results of a finished (or still-running) execution, computed from its Aggregate Report / Summary Report listener output: per-label and overall count, error rate, avg/min/max/median/p90/p95/p99 latency, throughput and KB/sec.