Skip to main content
Glama
Sign In

DistroKid MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get release status in DistroKid

distrokid_get_release_status
Read-onlyIdempotent

Get release status in the user's own DistroKid account from ChatGPT, Claude or any AI agent. Returns how to do it in DistroKid step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's DistroKid Cloud Browser. DistroKid's official API: DistroKid has no public API, no developer docs and no official MCP server (checked 28 Oct 2026).

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": "distrokid_get_release_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the read-only annotations, the description discloses key behavior: the tool opens nothing by itself, returns screen/button/field instructions, and DistroKid has no public API or official MCP server. That is useful operational context, though it does not detail authentication or what the step-by-step output looks like structurally.

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

Conciseness3/5

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

The core behavior is front-loaded, but the description contains avoidable phrasing such as 'from ChatGPT, Claude or any AI agent' and a dated API disclaimer that partly distracts from the tool's purpose. It is understandable but not tightly edited.

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 zero-parameter, read-only guidance tool with no output schema, the description supplies the essential context: it returns procedural instructions and the browser tools must perform the actual action. It is complete enough to call correctly, though it could clarify whether the guidance is generic or account/release-specific.

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

Parameters4/5

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

The tool has zero parameters, so there is no input schema burden to compensate for. The description does not need to explain parameters, and its mention of the user's own account is contextual rather than a parameter requirement.

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 DistroKid release-status task and explicitly says it returns step-by-step instructions rather than opening anything itself. That differentiates it from the cotlet_browser_* execution tools, but the 'Get release status' framing still sounds like data retrieval while the actual return is procedural guidance.

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 clearly tells the agent to use this tool first and then act through cotlet_browser_* tools in the DistroKid Cloud Browser. It gives strong context for when this tool is appropriate, though it does not explicitly exclude or compare against sibling distrokid_* tools such as distrokid_list_releases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DistroKid MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources