Skip to main content
Glama
Sign In

StreamElements MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Resolve store redemption in StreamElements

streamelements_resolve_store_redemption
Read-onlyIdempotent

Resolve store redemption in the user's own StreamElements account from ChatGPT, Claude or any AI agent. Returns how to do it in StreamElements step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's StreamElements Cloud Browser. StreamElements's official API: StreamElements has a full REST API (kappa v2) with a documented OAuth2 flow, but no official MCP server (checked 17 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": "streamelements_resolve_store_redemption"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond them: it performs no action, opens no page, returns screen/button/field-level instructions, and is meant to be followed by a separate browser-tool step. The API/OAuth note explains why automation rather than an API call is used, though it is dated trivia more than agent-relevant behavior.

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 message (returns a step-by-step guide, does not act, follow up with browser tools) is front-loaded and clear. But the opening marketing phrase "from ChatGPT, Claude or any AI agent" and the trailing paragraph about the StreamElements REST API and lack of an official MCP server are filler that does not help an agent decide or call correctly.

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 parameters and no output schema, the description carries the burden of explaining the return value, which it does (screens, buttons, fields) and it also clarifies the tool performs no action. It is nearly complete; the main omission is any precondition about account/login state needed for the redemption to exist.

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, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies no input is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does say it returns step-by-step instructions for resolving a store redemption, which is a specific resource and outcome. But the leading verb "Resolve" implies the tool performs the redemption, then the text immediately reverses that ("opens nothing by itself"), so the actual purpose -- producing a how-to guide -- only emerges in the second clause. It does distinguish itself from the cotlet_browser_* siblings, but the verb/resource framing is muddled.

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 an explicit workflow: call this to get the steps, then execute them with the cotlet_browser_* tools in the StreamElements Cloud Browser. That is a clear routing signal to the alternative tools. It stops short of stating prerequisites (e.g. that the user must be signed in and have a pending redemption) or any when-not-to-use case.

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

All StreamElements 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