Skip to main content
Glama

unblock

Bypass bot detection and anti-scraping measures to access web content, extract data, and capture screenshots from websites with protection mechanisms.

Instructions

Bypass bot detection and anti-scraping measures

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
contentNo
screenshotNo
stealthNo
blockAdsNo
headersNo

Implementation Reference

  • src/index.ts:191-204 (registration)
    Registration of the 'unblock' tool in the MCP server's listTools handler, defining name, description, and input schema.
    name: 'unblock',
    description: 'Bypass bot detection and anti-scraping measures',
    inputSchema: {
      type: 'object',
      properties: {
        url: { type: 'string' },
        content: { type: 'boolean' },
        screenshot: { type: 'boolean' },
        stealth: { type: 'boolean' },
        blockAds: { type: 'boolean' },
        headers: { type: 'object' },
      },
      required: ['url'],
    },
  • MCP server handler for the 'unblock' tool. Calls BrowserlessClient.unblock(), handles response including text content and binary screenshot, returns MCP content array.
    case 'unblock': {
      if (!args) throw new Error('Arguments are required');
      const result = await this.client!.unblock(args as any);
      if (result.success && result.data) {
        const content = [
          {
            type: 'text',
            text: 'Unblock operation completed successfully.',
          },
        ];
    
        if (result.data.content) {
          content.push({
            type: 'text',
            text: result.data.content,
          });
        }
    
        if (result.data.screenshot) {
          content.push({
            type: 'binary',
            mimeType: 'image/png',
            data: result.data.screenshot.toString('base64'),
          } as any);
        }
    
        return { content };
      } else {
        throw new Error(result.error || 'Failed to unblock');
      }
    }
  • Zod schema and TypeScript type for UnblockRequest used by the client.unblock method.
    export const UnblockRequestSchema = z.object({
      url: z.string(),
      browserWSEndpoint: z.boolean().optional(),
      cookies: z.boolean().optional(),
      content: z.boolean().optional(),
      screenshot: z.boolean().optional(),
      ttl: z.number().optional(),
      stealth: z.boolean().optional(),
      blockAds: z.boolean().optional(),
      headers: z.record(z.string()).optional(),
    });
    
    export type UnblockRequest = z.infer<typeof UnblockRequestSchema>;
  • TypeScript interface for UnblockResponse returned by the Browserless /unblock endpoint.
    export interface UnblockResponse {
      content?: string;
      screenshot?: Buffer;
      cookies?: Cookie[];
      browserWSEndpoint?: string;
    }
  • BrowserlessClient.unblock method that proxies the request to the Browserless server's /unblock HTTP endpoint via axios.
    async unblock(request: UnblockRequest): Promise<BrowserlessResponse<UnblockResponse>> {
      try {
        const response: AxiosResponse<UnblockResponse> = await this.httpClient.post('/unblock', request);
    
        return {
          success: true,
          data: response.data,
        };
      } catch (error) {
        return this.handleError(error);
      }
    }
Behavior1/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 mentions bypassing security measures but fails to describe critical behaviors: whether this is a read-only or mutating operation, what permissions or risks are involved, what the output looks like, or any rate limits. This is inadequate for a tool with potentially sensitive functionality.

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 states the core purpose without any fluff. It's appropriately sized and front-loaded, making it easy to parse quickly. Every word earns its place in conveying the tool's intent.

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 (bypassing security measures), lack of annotations, no output schema, and 6 parameters with 0% schema coverage, the description is incomplete. It doesn't address what the tool returns, how it behaves, or the semantics of its parameters, leaving significant gaps for the agent to operate effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for 6 parameters, the description adds no meaning beyond what the bare schema provides. It doesn't explain what 'content', 'screenshot', 'stealth', 'blockAds', or 'headers' do, or how they relate to bypassing detection. The description fails to compensate for the schema's lack of documentation.

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 with a specific verb ('bypass') and target ('bot detection and anti-scraping measures'), making it immediately understandable. However, it doesn't differentiate this tool from its siblings like 'get_content' or 'execute_browserql' that might also involve web access, so it doesn't reach the highest score.

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 'get_content' (which might fetch web content) and 'execute_browserql' (which might run browser queries), there's no indication of when 'unblock' is preferred or necessary, leaving the agent to guess based on context 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/Lizzard-Solutions/browserless-mcp'

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