Bug Bounty Assistant MCP

take_screenshot

Capture a browser screenshot of a target URL to visually inspect web pages during security assessments.

Instructions

Captures a browser snapshot of a page using Playwright

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "take_screenshot"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes	The target URL or domain

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

TDQS

C2.6/5.0

Behavior1/5

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

No annotations provided, so the description must bear full burden of behavioral disclosure. It mentions 'using Playwright' but fails to detail key behaviors like page load waiting, viewport settings, full-page vs viewport capture, or output format. This is severely insufficient for a screenshot tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence, 8 words), but it fails to include necessary information about behavior and output. While concise, it is not appropriately sized for the complexity of the tool, missing details that would aid the AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool performs a non-trivial action (Playwright screenshot), the description lacks essential context: no output schema or return value description, no mention of timeouts, page load state, or image format. This is inadequate for an agent to use the tool correctly.

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 one parameter 'target' with a description ('The target URL or domain'). Schema coverage is 100%, so the description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 action: capturing a browser snapshot using Playwright. The verb 'Captures' and resource 'browser snapshot of a page' are specific, and the tool is distinct from sibling tools (all security scanners, no screenshot tools), so no confusion.

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, common use cases, or when not to use it. Sibling tools are unrelated, so no differentiation needed, but still lacks usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server