Skip to main content
Glama
pvinis
by pvinis

playwright_get

Execute HTTP GET requests to retrieve data from specified URLs using a real browser environment, enabling interactions with web pages for testing, scraping, or content extraction.

Instructions

Perform an HTTP GET request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to perform GET operation

Implementation Reference

  • The execute method of GetRequestTool performs the HTTP GET request using the API context, retrieves the response text and status, and formats a success response.
    export class GetRequestTool extends ApiToolBase {
      /**
       * Execute the GET request tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (apiContext) => {
          const response = await apiContext.get(args.url);
          
          let responseText;
          try {
            responseText = await response.text();
          } catch (error) {
            responseText = "Unable to get response text";
          }
          
          return createSuccessResponse([
            `GET request to ${args.url}`,
            `Status: ${response.status()} ${response.statusText()}`,
            `Response: ${responseText.substring(0, 1000)}${responseText.length > 1000 ? '...' : ''}`
          ]);
        });
      }
    }
  • The input schema definition for the 'playwright_get' tool, specifying the required 'url' parameter.
      name: "playwright_get",
      description: "Perform an HTTP GET request",
      inputSchema: {
        type: "object",
        properties: {
          url: { type: "string", description: "URL to perform GET operation" }
        },
        required: ["url"],
      },
    },
  • Registration in the main tool handler switch statement that routes calls to 'playwright_get' to the GetRequestTool instance.
    case "playwright_get":
      return await getRequestTool.execute(args, context);
  • Instantiation of the GetRequestTool class instance used for handling 'playwright_get' calls.
    if (!getRequestTool) getRequestTool = new GetRequestTool(server);
  • Inclusion of 'playwright_get' in the API_TOOLS array for conditional browser/API context initialization.
    "playwright_get",
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 critical details: it doesn't mention if this opens a new page, handles redirects, includes headers, manages cookies, or returns response data. For an HTTP 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 extremely concise—a single, direct sentence with no wasted words. It's front-loaded with the core action, making it easy to parse quickly. Every word earns its place by conveying the essential purpose without fluff.

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 HTTP requests and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, response format, or integration with other Playwright tools (e.g., page state). For a tool that likely interacts with web pages, more context is needed to understand its full role and limitations.

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 schema description coverage is 100%, with the 'url' parameter clearly documented in the schema. The description doesn't add any meaning beyond what the schema provides—it doesn't explain URL format requirements, encoding, or base URL context. Given the high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 verb ('Perform') and resource ('HTTP GET request'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like playwright_post or playwright_navigate, which are also HTTP-related actions, so it doesn't fully distinguish itself within the family of Playwright tools.

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. With siblings like playwright_navigate (likely for page navigation) and playwright_post (for POST requests), there's no indication of context, prerequisites, or exclusions. It's a generic statement that offers no usage direction.

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

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