Skip to main content
Glama
Sign In
figma-slides-mcp

figma-slides-mcp

by luan007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Screenshot Slide

screenshot_slide

Get a PNG screenshot of any slide as a base64-encoded image. Useful for previewing slide content or verifying visual design.

Instructions

Capture a visual screenshot of a slide as PNG. Returns base64-encoded image.

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": {
      "slideId": "<slideId>"
    },
    "name": "screenshot_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoExport scale (1 = 1920x1080, 2 = 3840x2160). Default: 1
slideIdYesThe ID of the slide to screenshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the output format (PNG, base64) which is useful, but does not mention potential side effects, permissions, or constraints. It adds some behavioral context but not rich detail.

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, front-loaded sentence that efficiently communicates the tool's function and return format. Every word is meaningful and there is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter tool with full schema coverage, the description is mostly complete. It covers the core operation and return format, but could benefit from a note about when to prefer this over screenshot_all_slides.

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 coverage is 100% with descriptions for both slideId and scale. The description adds no additional parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool captures a visual screenshot of a slide as a PNG and returns a base64-encoded image. This specific verb+resource+format combination distinguishes it from sibling tools like screenshot_all_slides.

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 guidance is provided on when to use this tool versus alternatives such as screenshot_all_slides. The description only states the basic function without any context or exclusions.

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