Skip to main content
Glama
Sign In
Camoufox MCP

Camoufox MCP

by baixianger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

take_screenshot

Capture screenshots of web pages or specific elements using Camoufox MCP's anti-detection browser automation. Specify page areas, formats, and quality for documentation or analysis.

Instructions

Take a screenshot of the page or a specific element

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pageIdNoPage ID (uses active page if not specified)
fullPageNoCapture full scrollable page
uidNoElement UID to screenshot (from snapshot)
formatNopng
qualityNoQuality for JPEG/WebP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'take a screenshot' implies a read operation, the description doesn't mention whether this requires specific permissions, what format the output takes, whether it captures the current viewport or can capture scrolled content, or any rate limits or side effects.

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 gets straight to the point with zero wasted words. It's appropriately sized and front-loaded with the core functionality.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns (image data, file path, etc.), doesn't clarify behavioral aspects like whether it waits for page load, and provides minimal parameter guidance beyond the schema.

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?

With 80% schema description coverage, the baseline is 3. The description mentions 'page or a specific element' which hints at the pageId and uid parameters, but doesn't add meaningful semantic context beyond what the schema already documents for the 5 parameters.

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 ('take a screenshot') and target ('page or a specific element'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from similar sibling tools like 'take_snapshot' which might have overlapping functionality.

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, when not to use it, or what prerequisites might be needed. It simply states what the tool does without contextual usage information.

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

Deploy Server

Other Tools