Skip to main content
Glama
Sign In
podcli

podcli

by nmbrthirteen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_settings

Adjust rendering settings in the Web UI to control caption style, crop strategy, logo, and outro for podcast clips.

Instructions

Update rendering settings (caption style, crop strategy, logo, outro) in the Web UI.

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

Input Schema

NameRequiredDescriptionDefault
logo_pathNoPath or registered asset name for PNG logo
intro_pathNoPath or registered asset name for intro video
outro_pathNoPath or registered asset name for outro video
caption_styleNoCaption style
crop_strategyNoCropping strategy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv2.4.0
    • addedInput schema / properties / intro_path
      Added value: +{
+  "description": "Path or registered asset name for intro video",
+  "type": "string"
+}
  3. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, and the description only states the action 'update' without detailing side effects, reversibility, or what happens to existing settings. It is unclear whether this is a partial or full update, and there is no mention of the response or any error conditions.

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 a single, well-structured sentence that directly states the verb and object with a list of attributes. It is concise, with no unnecessary words or redundancy.

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 lack of annotations, the description is insufficient. It does not specify update semantics (partial vs. full replacement), prerequisites, or the expected response. It also omits the intro parameter. The agent would need to infer or inspect the schema to fully understand the tool's behavior.

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?

The schema provides brief descriptions for each parameter (e.g., 'Path or registered asset name for PNG logo' and 'Caption style'), covering all parameters. However, the description does not add extra context, and some parameters like intro_path are not mentioned. The schema descriptions are minimal and could be more informative.

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 identifies the action (update) and the resource (rending settings) and names several attributes (caption style, crop strategy, logo, outro). However, it omits intro_path, and the resource is not fully enumerated. The tool is still distinguishable from its siblings based on the listed attributes.

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 explicit conditions for when to use this tool are given. The description does not mention alternative tools or scenarios where this should be preferred over others like get_ui_state or manage_config. This leaves the agent without clear guidance on 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