Skip to main content

Energy Podcast Digest

by io.energypod

Overview Discussions Admin

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.

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

Input Schema

Name	Required	Description	Default
`lang`	No	Localized row titles in any supported language when the translations exist; omit for English
`slug`	No	YYYY-MM-DD edition date (from list_digests); omit for the latest
`region`	No	Regional reading list (na / emea / apac / latam); omit for the global edition

Output Schema

Name	Required	Description	Default
`lang`	No	The requested language (titles best-effort per row)
`digest`	Yes
`region`	Yes	The applied regional view ('' = the global edition)
`regions`	Yes	The edition's available regional views
`episodes`	Yes
`region_note`	Yes	Set when a requested region filter emptied the view

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedOutput schema / properties / digest / properties / slug / description

Previous value: -"YYYY-MM-DD edition date"New value: +"YYYY-MM-DD edition date, or SE-YYYY-MM-DD for a special edition"

Changed3 schema fields changedNov 7, 2026
- addedOutput schema / properties / digest / properties / edition_label
```
Added value: +{
+  "description": "public edition title; a special edition's own name",
+  "type": "string"
+}
```
- addedOutput schema / properties / digest / properties / special_edition
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / digest / properties / week_label / description
```
Added value: +"canonical ISO week label (Week 45 · 2026)"
```

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Localized row titles (es / zh) when the translations exist; omit for English"New value: +"Localized row titles in any supported language when the translations exist; omit for English"

changedInput schema / properties / lang / enum

Previous value: -[
-  "es",
-  "zh",
-  "hi",
-  "fr",
-  "ar"
-]New value: +[
+  "es",
+  "zh",
+  "hi",
+  "fr",
+  "ar",
+  "pt",
+  "ja"
+]

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Localized row titles in any supported language when the translations exist; omit for English"New value: +"Localized row titles (es / zh) when the translations exist; omit for English"

changedInput schema / properties / lang / enum

Previous value: -[
-  "es",
-  "zh",
-  "hi",
-  "fr",
-  "ar",
-  "pt"
-]New value: +[
+  "es",
+  "zh",
+  "hi",
+  "fr",
+  "ar"
+]

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Localized row titles (es / zh) when the translations exist; omit for English"New value: +"Localized row titles in any supported language when the translations exist; omit for English"

changedInput schema / properties / lang / enum

Previous value: -[
-  "es",
-  "zh",
-  "hi",
-  "fr",
-  "ar"
-]New value: +[
+  "es",
+  "zh",
+  "hi",
+  "fr",
+  "ar",
+  "pt"
+]

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "es",
-  "zh",
-  "hi",
-  "fr"
-]New value: +[
+  "es",
+  "zh",
+  "hi",
+  "fr",
+  "ar"
+]

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "es",
-  "zh"
-]New value: +[
+  "es",
+  "zh",
+  "hi",
+  "fr"
+]

Changed2 schema fields changedOct 13, 2026

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"
+}

Changed5 schema fields changedOct 13, 2026

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"
+]

Changed1 schema field changedSep 20, 2026

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"
+}

Changed2 schema fields changedSep 20, 2026

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: +[]

First observedSep 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), and the description adds genuinely useful behavior beyond them: the default-to-latest behavior when slug is omitted and the fact that the payload carries a 'regions' field listing what the edition offers. It stops short of disclosing ordering, size limits, or what happens for an invalid slug/region combination.

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 compact clauses, all load-bearing: the field list, the slug default, and the region semantics. The parenthetical '(title + show + published date + episode ids)' is dense but front-loaded and skimmable; nothing is redundant enough to cut.

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?

An output schema exists, so the description need not explain returns, yet it helpfully names the key fields. For a three-optional-parameter read tool with full enum documentation, the only real gap is the absence of any mention of the 'lang' parameter in prose, which is otherwise fully covered by the schema.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema for 'region' by equating it with the site's ?region= parameter and calling it the regional pilot, and it restates slug's latest-edition default with intent. 'lang' is not mentioned at all in the description, which keeps it from a 5.

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 names the resource precisely ('the episodes a given edition references') and enumerates the returned fields (title, show, published date, episode ids), which makes it distinguishable from get_episode at the single-vs-collection level. It does not name a sibling explicitly, so it falls short of full differentiation.

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?

'The cheapest way to map a week' gives a clear reason to prefer this tool over fetching episodes individually, and the description spells out the two default behaviors (omit slug for the latest edition, pass region for a regional list). It never states when to reach for list_digests or get_digest instead, so exclusions are left implicit.

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 tools Inspect

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

Need Help?