Skip to main content
Glama
titaniumtushar

burp-mcp-plus

repeater_from_template

Construct an HTTP request from a URL and custom fields, then send it to Burp Repeater. Optionally inherit headers, cookies, or authentication from a prior request for consistent testing.

Instructions

Send a request to Burp Repeater, built from scratch (URL + structured fields). Optionally inherit cookies/auth/UA from a history baseline.

Args: url: full URL, e.g. https://api.example.com/v1/users?id=1 method: HTTP method (default GET) headers: additional headers (overrides any inherited values) body: request body tab_name: Repeater tab label inherit_from_history_id: copy headers from this baseline first; the headers arg then overrides them. Host/Content-Length always re-derived from the new url+body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
methodNoGET
headersNo
bodyNo
tab_nameNo
inherit_from_history_idNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description explains key behavioral traits: inheritance mechanism (inherit_from_history_id copies headers, then headers arg overrides), automatic re-derivation of Host/Content-Length. However, it does not mention error handling, rate limits, or output behavior. Since no annotations are provided, the description shoulders the burden well but has minor gaps.

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 concise: a single-paragraph overview followed by a bulleted list of arguments. Every sentence adds value, and the structure is clear. No extraneous information.

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?

While parameter semantics are well-covered, the context is incomplete: no explanation of return values (though output schema exists, it's not referenced), no mention of prerequisites, error cases, or success cues. For a tool with 7 parameters and no annotations, more contextual completeness is needed.

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

Parameters5/5

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

With 0% schema description coverage, the description adds significant meaning for all parameters: URL includes an example, method default is stated, headers override inherited, body, tab_name, and inheritance mechanics are explained. This compensates fully for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Send' and the resource 'Burp Repeater', and specifies it's built from scratch with URL and structured fields. It distinguishes from siblings like 'repeater_from_history' by emphasizing 'from scratch' and optional inheritance.

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 for constructing a new request from scratch with optional inheritance, but does not explicitly state when to use this tool versus alternatives like 'send_request' or 'intruder_from_history'. No clear 'when not to use' guidance is provided.

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/titaniumtushar/burp-mcp-plus'

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