Capture a JPEG screenshot of the current Brave tab and return the image with its saved file path. Set fullPage to true to include the entire scrollable page.
JPEG screenshot of the current tab. Returns an image plus a saved file path.
| Name | Required | Description | Default |
|---|---|---|---|
| fullPage | No | Capture full scrollable page (default false) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations and no output schema, so the description carries the full behavioral burden. It usefully discloses the return shape (image plus saved file path), but says nothing about what determines the capture region (viewport vs full page), whether the page state is affected, or any permission/side-effect profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with zero padding; the core identification leads and the return-value note follows, so the reader gets the essentials immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-optional-param tool with no output schema, the description adequately covers what comes back and what is captured. However, it leaves the reader without the usage context needed to choose between it and browser_desktop_screenshot, which is a real gap given the crowded screenshot sibling set.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with a single optional boolean, so the schema already explains fullPage and its default. The description adds no parameter detail, which is acceptable at this coverage level but not additive.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('JPEG screenshot of the current tab'), which is enough to separate it from the sibling browser_desktop_screenshot (desktop capture) without opening a schema. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisites (e.g. a tab must be prepared/active), and no pointer to browser_desktop_screenshot as the alternative for desktop captures. The agent must guess which of the two screenshot tools applies.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.