Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

playlists_get_active_presentation_thumbnail

Retrieve thumbnail images for active playlist presentations in ProPresenter to preview content and verify display settings.

Instructions

Get thumbnail for active playlist presentation item

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": {
      "index": "<index>",
      "cueIndex": "<cueIndex>"
    },
    "name": "playlists_get_active_presentation_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesThe item index
cueIndexYesThe cue index within the item

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?

No annotations are provided, so the description carries full burden. It implies a read-only operation but does not disclose potential side effects, error conditions, or requirements for the active playlist.

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 concise phrase that is front-loaded and efficient. However, it sacrifices necessary detail for brevity.

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?

Given the complexity of accessing a thumbnail with two indices and the presence of many sibling tools, the description lacks essential context such as what the thumbnail represents, any constraints, or expected output format.

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 parameters having descriptions. The tool description adds no additional meaning beyond the schema, which is sufficient but not enhanced. 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 specifies 'Get thumbnail for active playlist presentation item', using a specific verb 'Get' and resource 'thumbnail' with context 'active playlist presentation item'. This distinguishes it from sibling tools like 'playlists_get_thumbnail' or 'playlists_get_active_announcement_thumbnail'.

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. It does not mention prerequisites like having an active presentation, nor does it explain the difference from similar thumbnail tools.

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