devtools-fleet-mcp

by pluginslab

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

screencast_start

Starts recording a screencast (video) of the target page.

Instructions

Starts recording a screencast (video) of the target page.

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": {
      "pageId": "<pageId>"
    },
    "name": "screencast_start"
  }
}

Input Schema

Name	Required	Description	Default
`pageId`	Yes	Targets a specific page by ID.
`filePath`	No	Output file path (.mp4). Uses mkdtemp to generate a unique path if not provided.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Oct 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The only annotation is readOnlyHint=false, so the description carries most of the burden. It establishes recording of the target page but says nothing about the recording continuing until screencast_stop, where output is written (beyond the schema's filePath note), or any disk/resource implications of an in-progress capture.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler. It is efficient, but the terseness borders on under-specification for a stateful operation that requires a paired stop call.

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?

Two simple parameters, no output schema, and a thin annotation set — the description is adequate to identify the action but leaves out lifecycle context (stop requirement, output location, page prerequisite) that an agent needs to drive 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?

Schema description coverage is 100%, with both pageId and filePath documented including the mkdtemp fallback behavior. The description adds nothing beyond the schema, so the baseline of 3 applies.

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?

Specific verb + resource + scope: 'Starts recording a screencast (video) of the target page.' It is clearly distinguishable from the sibling screencast_stop by the verb 'starts', though it never names that counterpart explicitly.

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 when-to-use guidance, no prerequisites (e.g., that a page must be selected), and no mention of the screencast_stop sibling that must eventually be called. Usage is only inferable from the verb.

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