Skip to main content
Glama

studio_capture_screenshot

Read-only

Wait for a specified revision to finish font and image rendering in a real browser, then capture an artboard or node as PNG and return revision, contentHash, and file SHA-256.

Instructions

严格等待指定 revision 在真实浏览器完成字体与图片渲染后截取画板或节点 PNG,返回 revision、contentHash 与文件 SHA-256。

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": "studio_capture_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
portNo
nodeIdNo
pageIdNo
outPathNo
revisionNo
timeoutMsNo
projectDirNo
includeImageNo默认 true,直接返回 MCP 图片供模型查看

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description still adds real behavioral value beyond them: it discloses that capture blocks until fonts and images finish rendering and that the response includes revision, contentHash and a file SHA-256. It does not mention that a PNG is written to outPath or what happens on timeout, which slightly strains the readOnly hint, but it never directly contradicts it.

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 dense sentence that front-loads the blocking render guarantee before the capture action and the return values. Zero filler, though the packing of precondition plus return contract into one clause costs some readability.

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?

With nine parameters, no output schema and near-zero schema description coverage, the description should carry much more. It states the return contract well but leaves the majority of inputs (port, projectDir, outPath, timeoutMs) and failure behavior unaddressed, so an agent cannot fully predict what a call will do.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 11 percent; only includeImage carries an inline description, and the description text does not compensate for the other eight parameters. It clarifies revision (must be the rendered one), node-versus-artboard selection, and the returned contentHash, but url, port, outPath, timeoutMs and projectDir remain undocumented in both places.

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 names a specific verb-plus-resource pair (capture artboard or node as PNG) and adds a precise precondition: the given revision must finish font and image rendering in a real browser. It also lists the return artifacts (revision, contentHash, file SHA-256). It stops short of naming a sibling such as studio_wait_for_render, so the 'this tool already blocks until render completes' distinction has to be inferred.

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?

There is no explicit when-to-use or when-not guidance. An agent cannot tell from the text whether to call studio_wait_for_render first, whether this call is safe to repeat for the same revision, or when to prefer studio_export_code or other export siblings. The only implicit usage cue is that a revision is required.

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