Skip to main content
Glama
nmbrthirteen

podcli

by nmbrthirteen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

manage_thumbnail_config

Show, export, import, reset, or set the thumbnail template podcli uses for generated podcast thumbnails, covering colors, fonts, frame, box, and single/pair layouts.

Instructions

Show, export, import, or reset the thumbnail template (colors, fonts, frame, box, layout) podcli uses to generate thumbnails. 'show' returns the effective config; 'export' writes it to a file path; 'import' replaces it from a file path; 'reset' reverts to the generic default; 'set_layout' picks the layout: 'single' (one face) or 'pair' (two people from the clip, guest left and host right, for interview clips; falls back to one face when podcli cannot tell two people apart).

Input Schema

NameRequiredDescriptionDefault
pathNoFile path for export (destination) or import (source)
actionYesConfig action
layoutNoFor set_layout. single: one face behind the headline. pair: the guest left and the host right, both from the clip's own footage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.8.0
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "show",
-  "export",
-  "import",
-  "reset"
-]New value: +[
+  "show",
+  "export",
+  "import",
+  "reset",
+  "set_layout"
+]
    • addedInput schema / properties / layout
      Added value: +{
+  "description": "For set_layout. single: one face behind the headline. pair: the guest left and the host right, both from the clip's own footage",
+  "enum": [
+    "single",
+    "pair"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv2.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose key mutating behavior: 'import' replaces the config, 'reset' reverts to the generic default, and the layout falls back to one face when podcli cannot distinguish two people. It omits details like whether export overwrites an existing file or whether import validates the source, keeping it from a 5.

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?

Actions are front-loaded and every clause carries information, but the body is one densely punctuated sentence and partially restates the layout enum already in the schema. It is efficient overall but slightly overloaded.

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?

With no output schema and no annotations, the description covers the action semantics and layout behavior well enough to call the tool correctly. It leaves the concrete return shape of 'show' implicit, a minor gap for an otherwise complete definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the pair-layout fallback behavior and the interview-clip intent (guest left, host right) that the enum descriptions do not fully capture.

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?

States a specific verb set and resource — the thumbnail template podcli uses to generate thumbnails — and enumerates all five actions, clearly distinguishing it from generic config siblings like manage_config and manage_env. An agent can identify the tool's domain without opening the schema.

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?

Breaks down when to use each action ('show' returns effective config, 'export' writes to a path, 'import' replaces, 'reset' reverts, 'set_layout' picks layout), which is clear contextual guidance. It does not name sibling alternatives or state exclusions, so it stops short of a 5.

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