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

figma-slides-mcp

by luan007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Screenshot All Slides

screenshot_all_slides

Capture thumbnails of every slide in a presentation and receive base64 PNG images for quick previews.

Instructions

Capture thumbnails of all slides. Returns array of base64 PNG images.

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

Input Schema

NameRequiredDescriptionDefault
scaleNoExport scale. Default: 0.5 (960x540 thumbnails)
maxSlidesNoMax slides to export. Default: 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavior: capturing thumbnails of all slides and returning an array of base64 PNG images. It doesn't mention side effects or performance caveats, but for a read-only operation this is reasonably transparent.

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 two short sentences, front-loaded with the primary action and return format. Every word earns its place—no filler or repetition.

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?

The tool is simple with two optional parameters, and the description covers the essential return value (base64 PNG array), which is needed since no output schema exists. It is complete enough for the complexity level, though it could briefly mention alternatives or performance limitations.

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% for both parameters, so the schema already explains scale and maxSlides. The description adds no additional parameter context beyond the schema, matching the baseline of 3.

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 'Capture thumbnails of all slides', a specific verb+resource+scope. This distinguishes it from sibling tools like screenshot_slide, which targets a single slide, by explicitly saying '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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the primary use case: when you need thumbnails of every slide. It doesn't explicitly name alternatives or exclude single-slide capture, but the context is clear on scope, so it earns a 4 for clear context without explicit 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