Skip to main content
Glama
Sign In

DistroKid MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Set splits in DistroKid

distrokid_set_splits
Read-onlyIdempotent

Set splits 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_set_splits"
  }
}

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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them by stating it 'opens nothing by itself'. It adds genuinely useful context beyond the annotations: why the browser path exists (no DistroKid public API, no official MCP server, verified date) and what the return value conceptually contains.

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 purpose is front-loaded, but 'from ChatGPT, Claude or any AI agent' is promotional filler and the dated API-verification parenthetical is bulky. The core actionable content (returns steps, opens nothing, then use cotlet_browser_*) could be stated in fewer words.

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?

With no output schema, the description must convey the return shape, and it does ('how to do it in DistroKid step by step (screens, buttons, fields)'). For a zero-parameter guidance tool this is essentially complete, short only of the split-format details or prerequisites the agent may need.

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 takes zero parameters and the schema is fully described, so there is no parameter meaning the description needs to carry. Baseline 4 applies.

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 ('Set splits in the user's own DistroKid account') and then clarifies the actual mechanism: it returns step-by-step guidance rather than performing the write. That clarification resolves the tension between the name and behavior, but it never names its closest sibling distrokid_get_splits to draw the read/write line 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 workflow: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the DistroKid Cloud Browser. What is missing is disambiguation from distrokid_get_splits and cotlet_app_guide, which plausibly overlap in what they return.

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