Skip to main content
Glama

Unfollow a podcast

unfollow_podcast
Idempotent

Stop following a podcast. Needs the "account" scope. Free.

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>"
    },
    "name": "unfollow_podcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
podcastYesA slug or podcast_id from find_podcasts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds valuable beyond-annotation context: the required "account" scope (auth requirement) and that the call is "Free" (cost). It still does not explain whether unfollowing is reversible, but most behavioral traits are already structured.

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

Conciseness5/5

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

Two short sentences with zero filler: action first, then required scope and cost. Every sentence earns its place for a tool this simple.

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

Completeness5/5

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

For a single-parameter mutation whose annotations already cover the safety profile, the description provides the action, required scope, and cost. Nothing essential for correct invocation is missing, and no output schema is needed for this simple operation.

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?

There is only one parameter, and the schema documents it fully (100% coverage) with "A slug or podcast_id from find_podcasts." The description adds no parameter meaning beyond the schema, which is the expected baseline when schema coverage is complete.

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?

The description gives a specific verb+resource ("Stop following a podcast") that is immediately distinguishable from the sibling follow_podcast. An agent can tell exactly what action this performs without opening the schema.

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?

The action is stated plainly, so the implied usage is clear, but there is no explicit when-to-use guidance, no prerequisite context beyond the account scope, and no named alternative for managing podcast follows. Adequate but minimal.

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