Skip to main content
Glama

Retry YouTube Playlist Assignment

postly_retry_youtube_playlists
Idempotent

Checks playlist membership and retries definite failed additions for an already uploaded video. Never uploads a video or resends an uncertain addition. Requires explicit user authorization to retry.

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": {
      "workspace_id": "<workspace_id>",
      "channel_id": "<channel_id>",
      "post_id": "<post_id>"
    },
    "name": "postly_retry_youtube_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
channel_idYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
assignmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare this is a non-readonly, idempotent, non-destructive, open-world operation, and the description adds meaningful behavior beyond that: it only retries *definite* failures, deliberately skips *uncertain* additions, and never performs the original upload. The explicit authorization requirement is also useful operational context. It does not describe what the response reports on partial failure.

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?

Three short sentences, front-loaded with the action, with each sentence adding a distinct constraint (scope, exclusions, authorization) and no repetition of the title.

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 no explanation, and the annotations plus description cover the mutation's risk profile and its boundaries well. The gap is parameter-level: for a mutation keyed on three opaque IDs, the description never explains how those IDs select the target video or playlist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and none of the three required parameters (workspace_id, channel_id, post_id) is mentioned or explained. The phrase 'for an already uploaded video' only loosely implies post_id, leaving an agent to infer how workspace/channel scope the retry.

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 pair and scope: 'Checks playlist membership and retries definite failed additions for an already uploaded video.' That is clearly distinct from the list-style sibling postly_list_youtube_playlists, though no sibling is named explicitly.

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 gives a clear precondition ('Requires explicit user authorization to retry') and a clear exclusion ('Never uploads a video or resends an uncertain addition'), so an agent knows both when to call it and what it will refuse to do. It stops short of naming an alternative tool for the upload case.

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