Skip to main content
Glama

playwright_patch

Send HTTP PATCH requests to update specific parts of web resources through browser automation, enabling partial modifications to existing data on servers.

Instructions

Perform an HTTP PATCH request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to perform PUT operation
valueYesData to PATCH in the body

Implementation Reference

  • The main handler logic for the 'playwright_patch' tool, which performs an HTTP PATCH request to the specified URL with the provided JSON data using Playwright's APIRequestContext and returns the response details.
    case "playwright_patch":
      try {
        var data = {
          data: args.value,
          headers: {
            'Content-Type': 'application/json'
          }
        };
        var response = await apiContext!.patch(args.url, data);
    
        return {
          content: [{
            type: "text",
            text: `Performed PATCH Operation ${args.url} with data ${JSON.stringify(args.value, null, 2)}`,
          }, {
            type: "text",
            text: `Response: ${JSON.stringify(await response.json(), null, 2)}`,
          }, {
            type: "text",
            text: `Response code ${response.status()}`
          }],
          isError: false,
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Failed to perform PATCH operation on ${args.url}: ${(error as Error).message}`,
          }],
          isError: true,
        };
      }
  • The input schema definition for the 'playwright_patch' tool, specifying required 'url' and 'value' parameters.
    {
      name: "playwright_patch",
      description: "Perform an HTTP PATCH request",
      inputSchema: {
        type: "object",
        properties: {
          url: { type: "string", description: "URL to perform PUT operation" },
          value: { type: "string", description: "Data to PATCH in the body" },
        },
        required: ["url", "value"],
      },
    },
  • Registration of the tool list handler, which exposes the 'playwright_patch' tool (included in the 'tools' array from createToolDefinitions) to the MCP client.
    // List tools handler
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: tools,
    }));
  • Helper array identifying 'playwright_patch' as an API tool, used to conditionally set up APIRequestContext without launching a browser.
    // API Request tools for conditional launch
    export const API_TOOLS = [
      "playwright_get",
      "playwright_post",
      "playwright_put",
      "playwright_delete",
      "playwright_patch"
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. It states the action but doesn't disclose behavioral traits such as error handling, authentication needs, rate limits, side effects (e.g., modifying page state), or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 no wasted words. It's appropriately sized and front-loaded, clearly stating the tool's purpose 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 complexity of an HTTP PATCH tool (a mutation operation) with no annotations and no output schema, the description is incomplete. It lacks details on behavior, error handling, and expected outcomes, making it insufficient for safe and effective use by an AI agent.

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%, so the schema already documents both parameters ('url' and 'value') adequately. The description doesn't add any meaning beyond what the schema provides, such as examples or constraints, but the baseline is 3 since the schema does the heavy lifting.

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

Purpose3/5

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

The description states the action ('Perform an HTTP PATCH request'), which is clear but generic. It doesn't specify what resource or domain this operates on (e.g., web pages, APIs), and while it distinguishes from siblings like 'playwright_get' or 'playwright_post' by specifying PATCH, it lacks specificity about the context (e.g., browser automation vs. general HTTP).

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a page loaded), exclusions, or comparisons to siblings like 'playwright_put' or 'playwright_post', leaving the agent to infer usage based on the HTTP method alone.

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

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/lars-hagen/mcp-playwright-cdp'

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