Skip to main content
Glama

playwright_put

Send HTTP PUT requests with specified data to a target URL using the MCP Playwright server, enabling browser automation and web interactions for efficient data updates.

Instructions

Perform an HTTP PUT request

Input Schema

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

Implementation Reference

  • The PutRequestTool.execute method implements the core logic for performing HTTP PUT requests using Playwright's APIRequestContext.put()
    export class PutRequestTool extends ApiToolBase {
      /**
       * Execute the PUT request tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (apiContext) => {
          // Check if the value is valid JSON if it starts with { or [
          if (args.value && typeof args.value === 'string' && 
              (args.value.startsWith('{') || args.value.startsWith('['))) {
            try {
              JSON.parse(args.value);
            } catch (error) {
              return createErrorResponse(`Failed to parse request body: ${(error as Error).message}`);
            }
          }
          
          const response = await apiContext.put(args.url, {
            data: args.value
          });
          
          let responseText;
          try {
            responseText = await response.text();
          } catch (error) {
            responseText = "Unable to get response text";
          }
          
          return createSuccessResponse([
            `PUT request to ${args.url}`,
            `Status: ${response.status()} ${response.statusText()}`,
            `Response: ${responseText.substring(0, 1000)}${responseText.length > 1000 ? '...' : ''}`
          ]);
        });
      }
    }
  • Tool definition including name, description, and input schema for 'playwright_put'.
    {
      name: "playwright_put",
      description: "Perform an HTTP PUT request",
      inputSchema: {
        type: "object",
        properties: {
          url: { type: "string", description: "URL to perform PUT operation" },
          value: { type: "string", description: "Data to PUT in the body" },
        },
        required: ["url", "value"],
      },
    },
  • Switch case dispatching 'playwright_put' tool calls to the PutRequestTool handler.
    case "playwright_put":
      return await putRequestTool.execute(args, context);
  • src/tools.ts:476-482 (registration)
    'playwright_put' listed in API_TOOLS array, used to determine API context initialization.
    export const API_TOOLS = [
      "playwright_get",
      "playwright_post",
      "playwright_put",
      "playwright_delete",
      "playwright_patch"
    ];
  • ApiToolBase abstract class providing safeExecute wrapper and API context validation used by PutRequestTool.
    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}`);
        }
      }
    } 
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 only states the action (HTTP PUT) without explaining what this entails—such as whether it's idempotent, requires authentication, handles errors, or modifies server state. 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—'Perform an HTTP PUT request' is front-loaded and appropriately sized for a simple tool. Every word earns its place, 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 this is a mutation tool (PUT implies write operation) with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like idempotency, error handling, or response format, which are crucial for an AI agent to use it correctly in a Playwright context.

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 both parameters ('url' and 'value') clearly documented in the schema. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Perform an HTTP PUT request' clearly states the verb (PUT) and resource (HTTP request), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'playwright_patch' or 'playwright_post', which are also HTTP methods, so it lacks sibling differentiation.

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 like 'playwright_patch' or 'playwright_post'. It doesn't mention typical use cases for PUT requests (e.g., updating resources) or prerequisites, leaving the agent to infer usage from 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

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/executeautomation/mcp-playwright'

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