Skip to main content
Glama

Podcast episode metadata

bpj_podcast_episode_metadata
Read-onlyIdempotent

Associate a series, episode number, audio file and duration in PodcastEpisode metadata.

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": {
      "name": "<name>",
      "series": "<series>",
      "episode": "<episode>",
      "seconds": "<seconds>",
      "audio": "<audio>"
    },
    "name": "bpj_podcast_episode_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
audioYes
seriesYes
episodeYes
secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description adds nothing beyond that — no statement of what the tool produces, whether inputs are validated against the min/max bounds, or what happens on failure.

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?

One short, front-loaded sentence with no filler. It is tight, though the brevity reflects missing content rather than disciplined editing.

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?

Five required parameters, no output schema, and no annotations gap, but the description never explains what the call yields or how the five fields combine into PodcastEpisode metadata. For a builder tool whose output shape is undefined, this leaves an agent guessing.

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

Parameters2/5

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

Schema description coverage is 0% (only field titles), so the description must compensate. It only restates four of the five fields (series, episode, audio, duration) and says nothing about the required "name" parameter, the audio URL format, or the 1–86400 second bound — added meaning beyond the titles is minimal.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource type ("PodcastEpisode metadata") and enumerates the fields being associated, which distinguishes it from the sibling metadata tools. But the verb "associate" is vague — it does not say whether this builds a schema.org JSON-LD object, validates fields, or stores a record.

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?

There is no when-to-use guidance, no preconditions, and no routing hint among the other *_metadata siblings. The agent must infer from the name alone that this is the podcast-episode case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.