Skip to main content
Glama

Energy Podcast Digest

by io.energypod
OverviewDiscussionsAdmin

List an edition's episodes

list_digest_episodes
Read-onlyIdempotent

The episodes a given edition references (title + show + published date + episode ids) — the cheapest way to map a week. Omitting slug returns the latest edition's episodes. Pass region for a region's reading list (the regional pilot, same as the site's ?region=); the payload's regions lists what the edition offers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLocalized row titles (es / zh) when the translations exist; omit for English
slugNoYYYY-MM-DD edition date (from list_digests); omit for the latest
regionNoRegional reading list (na / emea / apac / latam); omit for the global edition

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoThe requested language (titles best-effort per row)
digestYes
regionYesThe applied regional view ('' = the global edition)
regionsYesThe edition's available regional views
episodesYes
region_noteYesSet when a requested region filter emptied the view

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "es",
-  "zh"
-]New value: +[
+  "es",
+  "zh",
+  "hi",
+  "fr"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "Localized row titles (es / zh) when the translations exist; omit for English",
+  "enum": [
+    "es",
+    "zh"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / lang
      Added value: +{
+  "description": "The requested language (titles best-effort per row)",
+  "type": "string"
+}
  3. Changed5 schema fields changed
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Regional reading list (na / emea / apac / latam); omit for the global edition",
+  "enum": [
+    "na",
+    "emea",
+    "apac",
+    "latam"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / region
      Added value: +{
+  "description": "The applied regional view ('' = the global edition)",
+  "type": "string"
+}
    • addedOutput schema / properties / region_note
      Added value: +{
+  "description": "Set when a requested region filter emptied the view",
+  "type": "string"
+}
    • addedOutput schema / properties / regions
      Added value: +{
+  "description": "The edition's available regional views",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "digest",
-  "episodes"
-]New value: +[
+  "digest",
+  "region",
+  "region_note",
+  "regions",
+  "episodes"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "digest": {
+      "additionalProperties": false,
+      "properties": {
+        "as_of": {
+          "type": "string"
+        },
+        "episode_count": {
+          "type": "integer"
+        },
+        "slug": {
+          "description": "YYYY-MM-DD edition date",
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        },
+        "week_label": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "slug",
+        "week_label",
+        "as_of",
+        "episode_count",
+        "url"
+      ],
+      "type": "object"
+    },
+    "episodes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "api_url": {
+            "type": "string"
+          },
+          "duration_sec": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "eid": {
+            "type": "string"
+          },
+          "published": {
+            "type": "string"
+          },
+          "show": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "eid",
+          "title",
+          "show",
+          "published",
+          "url",
+          "api_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "digest",
+    "episodes"
+  ],
+  "type": "object"
+}
  5. Changed2 schema fields changed
    • changedInput schema / properties / slug / description
      Previous value: -"YYYY-MM-DD edition date"New value: +"YYYY-MM-DD edition date (from list_digests); omit for the latest"
    • changedInput schema / required
      Previous value: -[
-  "slug"
-]New value: +[]
  6. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds that the payload's 'regions' field lists what an edition offers and that region is 'the regional pilot,' which is genuine extra context, but the returned-field enumeration is largely redundant with the existing output schema.

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?

Three tight sentences, front-loaded with the resource and the default behavior. Every sentence carries information; only the parenthetical field list feels slightly padded given an output schema exists.

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 a full output schema, complete parameter descriptions, and safety annotations, the description only needs to cover defaults and the region semantics — which it does. The gap is the absence of sibling routing, which would complete an otherwise solid definition.

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% and both enums are documented in the schema, so the baseline is 3. The description reinforces slug as an edition date and clarifies that region mirrors the site's ?region= parameter, but adds little syntax or format detail beyond the schema.

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?

States a specific verb+resource — listing the episodes an edition references — and even names the returned fields (title, show, published date, episode ids). It frames itself as 'the cheapest way to map a week,' which hints at its niche among siblings, though it never names list_digests or get_digest directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear default behavior ('Omitting slug returns the latest edition's episodes') and when to pass region, but never states when to choose this tool over list_digests, get_digest, or get_episode. Usage is implied by the returned-field list rather than contrasted against alternatives.

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

All Energy Podcast Digest toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources