Skip to main content
Glama
darrenjrobinson

Entra.Chat Podcast MCP Server

by darrenjrobinson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_episode

Retrieve a specific Entra.Chat podcast episode by YouTube video ID or publication date, returning guests, chapters, timestamped links, and full transcript with time markers.

Instructions

Retrieve a specific Entra.Chat episode by YouTube video ID or publication date. Returns full metadata (guests with profile links, chapters with timestamped links) and the complete transcript with [mm:ss] time markers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD or YYYY-MM format to find the nearest episode (e.g. "2026-03" or "2026-03-15")
video_idNoYouTube video ID (11 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • removedInput schema / properties / episode_number
      Removed value: -{
-  "description": "Episode number (e.g. 12)",
-  "type": "number"
-}
  2. First observedv0.1.2

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Retrieve' implies a read-only operation and it describes the return contents, but it does not address permissions, rate limits, pagination, or error behavior. It adds useful output context but only partially covers behavioral traits.

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?

Two sentences, front-loaded with the core action and identifiers, then the return contents. Every sentence earns its place and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity retrieval tool with rich schema descriptions, the definition is complete. It explains the return payload even though no output schema exists, and the input semantics are covered by the schema.

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%, so the schema already documents both parameters in detail. The description adds that the lookup can be by video ID or publication date, but this is largely redundant with the schema descriptions.

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 states a specific verb and resource: retrieve a specific Entra.Chat episode. It clearly distinguishes itself from list/search siblings by emphasizing a single episode identified by video ID or publication date.

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?

It gives clear context for when to use it: when you have a YouTube video ID or publication date for a specific episode. However, it does not explicitly name alternatives such as list_episodes or search_entra_podcasts or state when not to use it.

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