Skip to main content
Glama

playwright_assert_response

Validate and assert the content of an HTTP response initiated in Playwright by specifying the response ID and expected data. Ensure accurate API or web interaction outcomes during browser automation.

Instructions

Wait for and validate a previously initiated HTTP response wait operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIdentifier of the HTTP response initially expected using `Playwright_expect_response`.
valueNoData to expect in the body of the HTTP response. If provided, the assertion will fail if this value is not found in the response body.

Implementation Reference

  • The AssertResponseTool class implements the core logic for the 'playwright_assert_response' tool, handling response waiting, validation against expected value, and returning success/error responses.
    export class AssertResponseTool extends BrowserToolBase {
      /**
       * Execute the assert response tool
       */
      async execute(args: AssertResponseArgs, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async () => {
          if (!args.id) {
            return createErrorResponse("Missing required parameter: id must be provided");
          }
    
          const responsePromise = responsePromises.get(args.id);
          if (!responsePromise) {
            return createErrorResponse(`No response wait operation found with ID: ${args.id}`);
          }
    
          try {
            const response = await responsePromise;
            const body = await response.json();
    
            if (args.value) {
              const bodyStr = JSON.stringify(body);
              if (!bodyStr.includes(args.value)) {
                const messages = [
                  `Response body does not contain expected value: ${args.value}`,
                  `Actual body: ${bodyStr}`
                ];
                return createErrorResponse(messages.join('\n'));
              }
            }
    
            const messages = [
              `Response assertion for ID ${args.id} successful`,
              `URL: ${response.url()}`,
              `Status: ${response.status()}`,
              `Body: ${JSON.stringify(body, null, 2)}`
            ];
            return createSuccessResponse(messages.join('\n'));
          } catch (error) {
            return createErrorResponse(`Failed to assert response: ${(error as Error).message}`);
          } finally {
            responsePromises.delete(args.id);
          }
        });
      }
    } 
  • MCP tool schema definition specifying the name, description, and input parameters (id required, value optional) for the tool.
    {
      name: "playwright_assert_response",
      description: "Wait for and validate a previously initiated HTTP response wait operation.",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "string", description: "Identifier of the HTTP response initially expected using `Playwright_expect_response`." },
          value: { type: "string", description: "Data to expect in the body of the HTTP response. If provided, the assertion will fail if this value is not found in the response body." }
        },
        required: ["id"],
      },
    },
  • Registration and dispatch in the main tool handler switch statement, routing tool calls to the AssertResponseTool's execute method.
    case "playwright_assert_response":
      return await assertResponseTool.execute(args, context);
  • src/tools.ts:463-463 (registration)
    The tool name is registered in the BROWSER_TOOLS array, enabling conditional browser launch for this tool.
    "playwright_assert_response",
  • Shared Map storing response promises keyed by ID, used by both expect_response and assert_response tools.
    const responsePromises = new Map<string, Promise<Response>>();
    
    interface ExpectResponseArgs {
      id: string;
      url: string;
    }
    
    interface AssertResponseArgs {
      id: string;
      value?: string;
    }
    
    /**
     * Tool for setting up response wait operations
     */
    export class ExpectResponseTool extends BrowserToolBase {
      /**
       * Execute the expect response tool
       */
      async execute(args: ExpectResponseArgs, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (page) => {
          if (!args.id || !args.url) {
            return createErrorResponse("Missing required parameters: id and url must be provided");
          }
    
          const responsePromise = page.waitForResponse(args.url);
          responsePromises.set(args.id, responsePromise);
    
          return createSuccessResponse(`Started waiting for response with ID ${args.id}`);
        });
      }
    }
    
    /**
     * Tool for asserting and validating responses
     */
    export class AssertResponseTool extends BrowserToolBase {
      /**
       * Execute the assert response tool
       */
      async execute(args: AssertResponseArgs, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async () => {
          if (!args.id) {
            return createErrorResponse("Missing required parameter: id must be provided");
          }
    
          const responsePromise = responsePromises.get(args.id);
          if (!responsePromise) {
            return createErrorResponse(`No response wait operation found with ID: ${args.id}`);
          }
    
          try {
            const response = await responsePromise;
            const body = await response.json();
    
            if (args.value) {
              const bodyStr = JSON.stringify(body);
              if (!bodyStr.includes(args.value)) {
                const messages = [
                  `Response body does not contain expected value: ${args.value}`,
                  `Actual body: ${bodyStr}`
                ];
                return createErrorResponse(messages.join('\n'));
              }
            }
    
            const messages = [
              `Response assertion for ID ${args.id} successful`,
              `URL: ${response.url()}`,
              `Status: ${response.status()}`,
              `Body: ${JSON.stringify(body, null, 2)}`
            ];
            return createSuccessResponse(messages.join('\n'));
          } catch (error) {
            return createErrorResponse(`Failed to assert response: ${(error as Error).message}`);
          } finally {
            responsePromises.delete(args.id);
          }
        });
      }
    } 
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 mentions waiting and validation, but lacks details on timeout behavior, error handling, or what happens if validation fails. This is inadequate for a tool that performs assertions with potential side effects.

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 that front-loads the core purpose without waste. Every word earns its place, making it highly concise and well-structured.

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?

Given no annotations and no output schema, the description is minimal. It covers the basic purpose but lacks behavioral details (e.g., what validation entails, error responses) and output expectations. This is adequate for a simple tool but leaves gaps in understanding its full operation.

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 fully documents the parameters. The description does not add meaning beyond the schema, such as explaining the relationship between 'id' and 'value' or validation specifics. Baseline 3 is appropriate as the schema handles 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 clearly states the tool's purpose: 'Wait for and validate a previously initiated HTTP response wait operation.' It specifies the verb ('wait for and validate') and resource ('HTTP response'), but does not explicitly differentiate from sibling tools like 'playwright_expect_response' beyond implying a sequence.

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

Usage Guidelines3/5

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

The description implies usage context by referencing 'previously initiated' with 'playwright_expect_response', suggesting this tool follows that one. However, it does not provide explicit when-to-use guidance, alternatives, or exclusions, leaving the agent to infer the workflow.

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