Skip to main content
Glama

PostPod

List episodes

list_episodes
Read-onlyIdempotent

List recent daily episodes for this account, newest delivery date first. This does not generate an episode. Use generate_episode to start today's episode.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 largely covered. The description adds real value with result ordering and an explicit no-side-effect clarification, but says nothing about result volume or bounds on 'recent,' which is the main unknown for a parameterless list call.

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 short sentences, front-loaded with the resource and ordering before the disambiguation. Nothing is padded, though the second and third sentences partly restate each other: both are about not generating an episode.

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

Completeness3/5

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

For a zero-parameter read tool with full annotations and no output schema, the description covers purpose, ordering, and the main sibling confusion. It falls short on the two things an agent cannot infer: how many episodes are returned and whether a bound or offset exists for going further back.

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?

The tool takes zero parameters, so the schema already carries the full surface (additionalProperties false, empty properties). The description adds no parameter meaning because there is none to add; baseline applies.

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?

States a specific verb and resource ('List recent daily episodes'), scopes it ('for this account'), and specifies ordering ('newest delivery date first'). It explicitly carves itself away from the sibling that generates episodes, so an agent can distinguish it from generate_episode without opening a schema.

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?

Explicitly names the alternative and its condition: 'Use generate_episode to start today's episode,' plus a negative exclusion ('This does not generate an episode'). What is left implicit is usage-relevant: how many 'recent' episodes come back and whether any paging/cursor exists, which matters with zero parameters.

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.

Resources