Skip to main content
Glama

playwright_delete

Execute an HTTP DELETE request on a specified URL using the Playwright MCP Server, enabling browser automation for web interactions and content removal.

Instructions

Perform an HTTP DELETE request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to perform DELETE operation

Implementation Reference

  • DeleteRequestTool class: executes the playwright_delete tool by sending a DELETE HTTP request using Playwright's APIRequestContext, retrieves response status and body (truncated), and returns formatted success response.
    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;
          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 definition with input schema for 'playwright_delete': requires 'url' parameter.
    {
      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/registration in toolHandler switch statement: routes 'playwright_delete' calls to DeleteRequestTool.execute()
    case "playwright_delete":
      return await deleteRequestTool.execute(args, context);
  • Instantiation of DeleteRequestTool instance during tool initialization.
    if (!deleteRequestTool) deleteRequestTool = new DeleteRequestTool(server);
  • Included in API_TOOLS array for conditional API context setup.
    "playwright_delete",
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 the action but lacks details on side effects (e.g., data deletion, idempotency), authentication needs, error handling, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, front-loading the core action. It's appropriately sized for a simple tool, making it easy to parse without unnecessary elaboration.

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 (a mutation operation with potential side effects), lack of annotations, and no output schema, the description is incomplete. It doesn't address critical aspects like what the tool returns, error conditions, or behavioral constraints, leaving the agent with insufficient context for reliable use.

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?

The input schema has 100% description coverage, with the 'url' parameter clearly documented as 'URL to perform DELETE operation'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema 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') with a specific verb ('Perform') and resource type ('HTTP DELETE request'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like playwright_patch, playwright_post, or playwright_put, which are also HTTP methods but for different operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios for DELETE requests (e.g., deleting resources), prerequisites, or how it differs from other HTTP methods in the sibling list, leaving the agent to infer usage based on general HTTP knowledge.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BhanuTJ93/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server