Spoken

List followed shows

list_following

Read-onlyIdempotent

The shows this key is kept current on. Every charged fetch makes its show a follow: the five most-fetched shows from the last 180 days are followed automatically (source 'fetch'), and up to 25 more can be declared with follow_podcast (source 'explicit'). Muted shows are listed separately. Use list_new_episodes to see what is new on them. Does not consume credits; the demo key has nothing to follow with.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`muted`	Yes
`limits`	Yes
`following`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "following": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "fetch_count": {
+            "description": "Episodes of this show fetched.",
+            "type": "number"
+          },
+          "last_fetched_at": {
+            "type": "string"
+          },
+          "newest_fetched_id": {
+            "description": "Newest episode fetched; list_new_episodes lists what came after it.",
+            "type": "string"
+          },
+          "podcast": {
+            "description": "Show name.",
+            "type": "string"
+          },
+          "podcast_id": {
+            "description": "Show id; pass it to list_episodes or follow_podcast.",
+            "type": "string"
+          },
+          "source": {
+            "description": "'fetch': followed automatically from fetches. 'explicit': declared with follow_podcast.",
+            "enum": [
+              "fetch",
+              "explicit"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "podcast_id",
+          "podcast",
+          "source",
+          "fetch_count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limits": {
+      "additionalProperties": false,
+      "properties": {
+        "explicit": {
+          "description": "Most shows that can be declared with follow_podcast.",
+          "type": "number"
+        },
+        "inferred": {
+          "description": "Shows followed automatically from fetches.",
+          "type": "number"
+        },
+        "inferred_window_days": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "explicit",
+        "inferred",
+        "inferred_window_days"
+      ],
+      "type": "object"
+    },
+    "muted": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "podcast": {
+            "description": "Show name.",
+            "type": "string"
+          },
+          "podcast_id": {
+            "description": "Show id; pass it to list_episodes or follow_podcast.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "podcast_id",
+          "podcast"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "following",
+    "muted",
+    "limits"
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the description does not consume credits, the demo key has nothing to follow, the 5-auto / 25-explicit follow caps, the 180-day window, and that muted shows appear in a separate section. These are non-obvious traits not derivable from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Most sentences carry real payload (source semantics, caps, credit cost, alternative tool), but the opening sentence is confusingly phrased and the 'every charged fetch makes its show a follow' clause takes a second read to parse. Information is not cleanly front-loaded around the core action of listing.

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 return values need not be explained, and the description covers the important ambient facts: follow sources, muted separation, credit cost, and where to go next. The only gap is the fuzzy lead sentence, which slightly obscures what exactly is returned as the primary list.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate at the parameter level; the baseline for a parameterless tool is 4. The description correctly implies a bare, no-argument call.

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 identifies the resource (the shows this key is kept current on) and, more usefully, defines what a 'follow' actually means here — automatic follows from charged fetches (source 'fetch') versus declared follows via follow_podcast (source 'explicit'). The opening clause 'The shows this key is kept current on' is grammatically awkward and never states a clean verb like 'lists', but the follow semantics make the resource unambiguous and distinguishable from siblings.

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 explicitly routes the agent to two siblings: follow_podcast to declare additional follows, and list_new_episodes to see what is new on the followed shows. It also notes muted shows are listed separately. It does not state an explicit when-not-to-use condition beyond the demo-key caveat, so it falls short of full 5-level routing.

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

All Spoken tools Inspect

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.