Skip to main content
Glama

playwright_delete

Send HTTP DELETE requests to remove resources from web applications using browser automation. Specify the target URL to delete data or clear content programmatically.

Instructions

Perform an HTTP DELETE request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to perform DELETE operation

Implementation Reference

  • DeleteRequestTool class implements the core logic for the 'playwright_delete' tool. It performs an HTTP DELETE request using Playwright's APIRequestContext.delete(), handles response text, and formats the success response with status and truncated body.
    export class DeleteRequestTool extends ApiToolBase {
      /**
       * Execute the DELETE request tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (apiContext) => {
          const response = await apiContext.delete(args.url);
    
          let responseText: string;
          try {
            responseText = await response.text();
          } catch (_error) {
            responseText = "Unable to get response text";
          }
    
          return createSuccessResponse([
            `DELETE request to ${args.url}`,
            `Status: ${response.status()} ${response.statusText()}`,
            `Response: ${responseText.substring(0, 1000)}${responseText.length > 1000 ? "..." : ""}`,
          ]);
        });
      }
    }
  • Tool metadata definition including name, description, and input schema (requires 'url' string) for MCP protocol tool listing and validation.
    {
      name: "playwright_delete",
      description: "Perform an HTTP DELETE request",
      inputSchema: {
        type: "object",
        properties: {
          url: { type: "string", description: "URL to perform DELETE operation" },
        },
        required: ["url"],
      },
    },
  • Dispatch switch case in handleToolCall that routes 'playwright_delete' calls to the DeleteRequestTool instance's execute method.
    case "playwright_delete":
      return await deleteRequestTool.execute(args, context);
  • Instantiation of DeleteRequestTool instance during tool initialization in initializeTools function.
    if (!deleteRequestTool) deleteRequestTool = new DeleteRequestTool(server);
  • ApiToolBase abstract class provides common API context validation, error handling, and safeExecute wrapper used by DeleteRequestTool.
    import type { APIRequestContext } from "playwright";
    import { createErrorResponse, type ToolContext, type ToolHandler, type ToolResponse } from "../common/types.js";
    
    /**
     * Base class for all API-based tools
     * Provides common functionality and error handling
     */
    export abstract class ApiToolBase implements ToolHandler {
      protected server: any;
    
      constructor(server: any) {
        this.server = server;
      }
    
      /**
       * Main execution method that all tools must implement
       */
      abstract execute(args: any, context: ToolContext): Promise<ToolResponse>;
    
      /**
       * Ensures an API context is available and returns it
       * @param context The tool context containing apiContext
       * @returns The apiContext or null if not available
       */
      protected ensureApiContext(context: ToolContext): APIRequestContext | null {
        if (!context.apiContext) {
          return null;
        }
        return context.apiContext;
      }
    
      /**
       * Validates that an API context is available and returns an error response if not
       * @param context The tool context
       * @returns Either null if apiContext is available, or an error response
       */
      protected validateApiContextAvailable(context: ToolContext): ToolResponse | null {
        if (!this.ensureApiContext(context)) {
          return createErrorResponse("API context not initialized");
        }
        return null;
      }
    
      /**
       * Safely executes an API operation with proper error handling
       * @param context The tool context
       * @param operation The async operation to perform
       * @returns The tool response
       */
      protected async safeExecute(
        context: ToolContext,
        operation: (apiContext: APIRequestContext) => Promise<ToolResponse>,
      ): Promise<ToolResponse> {
        const apiError = this.validateApiContextAvailable(context);
        if (apiError) return apiError;
    
        try {
          return await operation(context.apiContext!);
        } catch (error) {
          return createErrorResponse(`API operation failed: ${(error as Error).message}`);
        }
      }
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose effects (e.g., data deletion, side effects), authentication needs, error handling, or response format, which are critical for a destructive operation like DELETE.

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, efficient sentence with zero waste, clearly front-loaded with the core action. It's appropriately sized for a simple tool, making it easy 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?

Given the tool's complexity (HTTP DELETE is a destructive operation) and lack of annotations or output schema, the description is incomplete. It fails to address key aspects like what the tool returns, error conditions, or safety warnings, leaving significant gaps for agent understanding.

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 description coverage is 100%, with the 'url' parameter documented in the schema. The description adds no additional meaning beyond what the schema provides, such as URL format examples or constraints, so it meets the baseline for high coverage without extra value.

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?

The description clearly states the action ('Perform an HTTP DELETE request'), which is a specific verb. It distinguishes from siblings like playwright_post or playwright_put by specifying the HTTP method, but doesn't explicitly mention the resource being deleted (e.g., web content or API endpoint), keeping it slightly generic.

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 guidance on when to use this tool versus alternatives is provided. It doesn't mention scenarios for DELETE requests (e.g., deleting resources in REST APIs) or differentiate from other HTTP methods in the sibling list, leaving usage context implied but unspecified.

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