Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_presentation_thumbnail

Extract a thumbnail image for a specific slide in a ProPresenter presentation using slide index and presentation UUID.

Instructions

Get a thumbnail for a specific slide in a presentation

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": {
      "presentationUuid": "<presentationUuid>",
      "index": "<index>"
    },
    "name": "get_presentation_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
presentationUuidYesThe UUID of the presentation
indexYesThe slide index (0-based)
qualityNoOptional quality setting for the thumbnail

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It only states 'Get a thumbnail' without explaining if it's read-only, what the output format is, error handling, or side effects. The verb 'Get' implies read-only but lacks confirmation.

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?

The description is a single, clear sentence with no unnecessary words. While it is concise, it sacrifices valuable information that could be included without bloat.

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?

Despite low complexity (3 params, no output schema, no annotations), the description is too sparse. It omits crucial context like thumbnail format, quality range, and behavior when the slide doesn't exist, leaving the agent underinformed.

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%, so the schema already explains all parameters (presentationUuid, index, quality). The description adds no extra meaning beyond what the schema provides, meeting the baseline.

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 verb 'Get' and the resource 'thumbnail for a specific slide in a presentation', making it distinct from sibling tools that deal with presentations or thumbnails at different levels.

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 (e.g., playlists_get_thumbnail, themes_get_slide_thumbnail) or any prerequisites like the presentation being loaded.

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