Camoufox MCP

Overview Schema Source Related Servers Discussions Admin

press_key

Simulate keyboard input to interact with web pages through anti-detection browser automation, enabling human-like key presses and combinations for automated tasks.

Instructions

Press a keyboard key or combination

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": {
      "key": "<key>"
    },
    "name": "press_key"
  }
}

Input Schema

Name	Required	Description	Default
`pageId`	No	Page ID (uses active page if not specified)
`key`	Yes	Key to press (e.g., "Enter", "Tab", "Control+a")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Feb 2, 2026

TDQS

C2.9/5.0

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 states the action ('press') but doesn't describe what happens after pressing (e.g., does it trigger events, is it synchronous/asynchronous, are there side effects like navigation). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 no annotations, no output schema, and a mutation tool (implied by 'press'), the description is incomplete. It doesn't cover behavioral aspects like error handling, return values, or interaction with sibling tools, leaving gaps for the agent to navigate usage effectively.

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?

Schema description coverage is 100%, so the schema already documents both parameters ('pageId' and 'key') with clear descriptions. The description adds no additional meaning beyond the schema, such as examples beyond 'Enter' or 'Tab', or context for key combinations. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('press') and resource ('keyboard key or combination'), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'click' or 'fill', but the verb 'press' versus 'click' or 'fill' provides some implicit distinction for keyboard interactions versus mouse or form actions.

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 like 'click' for mouse actions or 'fill' for text input. It doesn't mention prerequisites (e.g., needing an active page) or exclusions, leaving the agent to infer usage from context alone.

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