Skip to main content
Glama

burp_spider

Crawl websites to map application structure and identify content for security testing using Burp Suite's spidering capabilities.

Instructions

Spider/crawl target using Burp Suite

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget URL to spider

Implementation Reference

  • Core handler function that executes the Burp Suite spider/crawl using the REST API on the provided target URL, waits for completion, and returns discovered URLs.
    async spiderTarget(target: string): Promise<any> {
      try {
        console.error(`🕷️ Spidering target: ${target}`);
    
        const spiderResponse = await axios.post(`${this.apiBaseUrl}/v0.1/spider`, {
          base_url: target
        });
    
        const spiderTaskId = spiderResponse.data.task_id;
        
        // Wait for spider completion
        await this.waitForTaskCompletion(spiderTaskId, 600000); // 10 min timeout
    
        // Get spider results
        const spiderResults = await axios.get(`${this.apiBaseUrl}/v0.1/spider/${spiderTaskId}`);
    
        return {
          task_id: spiderTaskId,
          status: spiderResults.data.status,
          urls_found: spiderResults.data.urls || []
        };
    
      } catch (error) {
        console.error('Spider failed:', error);
        return { error: error instanceof Error ? error.message : String(error) };
      }
    }
  • src/index.ts:456-466 (registration)
    Registers the 'burp_spider' tool in the MCP server's tool list, including its schema for input validation.
    {
      name: "burp_spider",
      description: "Spider/crawl target using Burp Suite",
      inputSchema: {
        type: "object",
        properties: {
          target: { type: "string", description: "Target URL to spider" }
        },
        required: ["target"]
      }
    },
  • Switch case in the main tool dispatcher that routes 'burp_spider' calls to the BurpSuiteIntegration instance's spiderTarget method.
    case "burp_spider":
      return respond(await this.burpSuite.spiderTarget(args.target));
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 mentions 'spider/crawl' which implies a potentially resource-intensive or intrusive operation, but fails to detail aspects like required permissions, rate limits, output format, or whether it's destructive. This leaves significant gaps for an agent to understand the tool's behavior.

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 with a single, direct sentence that front-loads the core functionality. There's no wasted verbiage, making it efficient for quick comprehension by an AI agent.

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 implied by a crawling tool in a security testing context, no annotations, no output schema, and incomplete behavioral disclosure, the description is inadequate. It doesn't cover critical aspects like what the tool returns, error conditions, or how it integrates with other Burp Suite tools, leaving the agent with insufficient 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?

The input schema has 100% description coverage, with the 'target' parameter clearly documented. The description adds no additional semantic context beyond what the schema provides, such as URL format examples or crawling depth. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 action ('spider/crawl') and target ('using Burp Suite'), providing a specific verb and resource. However, it doesn't explicitly differentiate from sibling tools like 'burp_active_scan' or 'directory_scan', which might also involve crawling or scanning behavior, 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 offers no guidance on when to use this tool versus alternatives. With many sibling tools like 'burp_active_scan', 'directory_scan', and 'nmap_scan' that might overlap in web assessment contexts, there's no indication of specific use cases, prerequisites, or exclusions.

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/adriyansyah-mf/mcp-pentest'

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