Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

playlists_get_active_announcement_thumbnail

Retrieve thumbnail images for active announcement playlist items in ProPresenter to verify visual content before display.

Instructions

Get thumbnail for active playlist announcement 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_announcement_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

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states 'Get thumbnail', implying a read-only operation, but fails to mention error conditions (e.g., no active announcement, invalid indices), side effects, or output format.

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 sentence, concise and front-loaded with the key action. It could benefit from slightly more detail, but there is no redundant information.

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 no output schema and no annotations, the description should outline return value, error handling, and when to use. It lacks this information, making it insufficient for an agent to reliably invoke and interpret results.

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%, and the description adds minimal meaning beyond the schema's descriptions ('The item index', 'The cue index within the item'). The overview labeling of 'active playlist announcement item' provides context but no new parameter-level detail.

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 clearly states the action ('Get thumbnail') and the resource ('for active playlist announcement item'). However, it does not explain what 'active' refers to (e.g., current active playlist) and fails to differentiate from sibling tools like 'playlists_get_active_presentation_thumbnail' or 'playlists_get_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. Siblings like 'announcement_get_active' or 'playlists_get_active_presentation_thumbnail' exist, but the description offers no context for selection.

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