Skip to main content
Glama
Sign In
jmeter-mcp-server

jmeter-mcp-server

by IAnjaniKr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

delete_element

Delete a named element from a JMeter test plan (.jmx) file by specifying the file path and element name.

Instructions

Delete an element from a test plan by name

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "testfile": "<testfile>",
      "elementName": "<elementName>"
    },
    "name": "delete_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
testfileYesPath to the .jmx file
elementNameYesName of the element to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool deletes an element by name, but it does not mention whether deletion is permanent, whether it affects child elements, whether changes are persisted to the test file, or what happens if the element is not found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single direct sentence with no filler. The action verb and resource are front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with no annotations and no output schema, the description is thin on consequences such as irreversibility, side effects, persistence, or error behavior. The parameters are clear, but the behavioral context is not complete enough for an agent to fully anticipate the tool's impact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with both testfile and elementName already described in the input schema. The description's phrase 'by name' aligns with elementName but adds no material semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Delete') and a clear resource ('an element from a test plan'), with the selection mechanism ('by name') stated. This clearly distinguishes it from sibling tools such as add_http_sampler, update_thread_group, and read_test_file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the intended use case—removing a named element from a .jmx test plan—but does not explicitly state when to use this tool versus alternatives. There are no exclusions or conditions provided, so the guidance is adequate but largely implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools