Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dev.to podcast episodes

dev_to_podcast_episodes_list
Read-onlyIdempotent

List episodes from a Dev.to podcast by providing its podcast slug, with pagination via page and limit. Use it to retrieve and browse a podcast's episode catalog.

Instructions

List the episodes of a podcast hosted on Dev.to. Requires podcast. Returns a list (use page when paginated).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "podcast": "<podcast>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_podcast_episodes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-1000). Default: 1. A full page may be followed by an empty page when the list ends exactly at a page boundary.
limitNoRows per page (1-1000). Default: 30. A page is the same price at any size.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
podcastYesRequired. Podcast slug, e.g. `codenewbie`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish this as a read-only, idempotent, open-world operation. The description adds useful but limited behavioral detail: it returns a list and pagination may be needed. It does not discuss authentication, result size, or ordering, so it remains adequate rather than rich.

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?

The description is short and front-loaded, stating the core operation before the requirement and return shape. The phrase "use page when paginated" is slightly circular, but no sentence is clearly wasteful.

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?

For a straightforward list tool with a fully described schema and strong read-only annotations, the description covers the essentials: what it lists, the required podcast identifier, and pagination hints. The remaining details are adequately handled by structured fields, though the description could mention ordering or empty results.

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 all parameter semantics are already fully documented in the schema. The description adds only marginal emphasis by calling out `podcast` as required and pointing to `page` for pagination, which is consistent with the baseline for high-coverage schemas.

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 states a specific verb and resource: listing episodes of a Dev.to-hosted podcast. It is clearly distinct from a single-episode getter, though it does not explicitly differentiate itself from sibling list tools.

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?

It specifies that `podcast` is required and mentions using `page` when paginated, which gives basic invocation context. However, it provides no explicit when-not guidance or comparison to related tools such as the episode detail tool.

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