MCP Server By TestMu AI

Delete Prerun File

deletePrerunFile

Destructive

Delete an uploaded prerun file by stored TestMu AI file path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deletePrerunFile"
  }
}

Input Schema

Name	Required	Description	Default
`filePath`	No	Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)
`file_path`	No	Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

changedInput schema / properties / filePath / description

Previous value: -"Stored LambdaTest file path to delete"New value: +"Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)"

changedInput schema / properties / file_path / description

Previous value: -"Stored LambdaTest file path to delete"New value: +"Stored path of the pre-run or post-run file, as uploadPrerunFile returns it (<name>/pre/<file> or <name>/post/<file>)"

First observedOct 5, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is given. The description adds that the target is located 'by stored file path', but says nothing about irreversibility, confirmation, or behavior on a missing path — useful context that is left out.

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?

A single, front-loaded sentence with no filler; the verb and resource lead the description.

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

Completeness3/5

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

Destructive annotations and a fully documented schema make the definition minimally sufficient, and no output schema is needed. However, for an irreversible delete it omits failure behavior and the duplicate-parameter ambiguity, leaving gaps an agent could stumble on.

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% and the schema already explains the path format returned by uploadPrerunFile. The description only restates 'stored TestMu AI file path' and does not address why both filePath and file_path exist or which to supply, so it adds little beyond the schema.

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

Purpose4/5

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

States a specific verb (delete) and resource (uploaded prerun file), scoped to a stored TestMu AI file path. It is clearly distinct from deleteBuild/deleteSession/deleteUploadedApps, but it never explicitly contrasts with the closest sibling, deleteUserFile.

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

Usage Guidelines2/5

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

No statement of when to use this versus deleteUserFile or deleteUploadedApps, and no prerequisites (e.g. that the path must come from uploadPrerunFile). Usage is only inferable from the tool name.

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

All MCP Server By TestMu AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?