Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dev.to podcast episode

dev_to_podcast_episode_get
Read-onlyIdempotent

Fetch a Dev.to podcast episode's audio, publish date, and show notes by path or URL to access complete episode details.

Instructions

Get a Dev.to podcast episode's audio, publish date and show notes. Requires path.

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": {
      "path": "<path>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dev_to_podcast_episode_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRequired. Episode path, e.g. `/codenewbie/s27e8-learning-ai-matt-eland`. The episode URL is also accepted.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful detail of what content is returned (audio, publish date, show notes), but says nothing about missing-episode behavior, error handling, or auth needs.

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?

Two short sentences, front-loaded with the outcome and the one prerequisite. The 'Requires `path`' clause is largely redundant against the schema's required list, which keeps it from a perfect score.

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?

This is a simple single-resource read with rich annotations, so little is needed, and naming the returned fields substitutes for the absent output schema. Still, the description is thin on the analytics/context parameters that make up most of the required set, leaving the definition adequate but not complete.

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 four parameters are already documented in the schema, including the path format and URL alternative. The description only repeats the `path` requirement and actually undercounts the required set (context and llm_model are also required), adding no real meaning 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 ('Get') and resource ('a Dev.to podcast episode') and enumerates what comes back: audio, publish date, show notes. It is clearly distinguishable from dev_to_podcast_episodes_list by the singular episode framing, though it never names that sibling explicitly.

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?

Usage is only implied: fetching one episode by path versus browsing a list. There is no explicit when-to-use/when-not statement and no mention of the alternative list tool, so the agent must infer the routing itself.

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