Uscreen MCP Server and API by Cotlet

Get analytics in Uscreen

uscreen_get_analytics

Read-onlyIdempotent

Get analytics in the user's own Uscreen account from ChatGPT, Claude or any AI agent. Returns how to do it in Uscreen step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Uscreen Cloud Browser. Uscreen's official API: Yes, in part: Uscreen has a Publisher API for stores on UscreenPlus that manages customers, access, subscriptions, groups and invoices and only reads videos, collections and live events (checked 11 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": "uscreen_get_analytics"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context: it 'opens nothing by itself' and returns screens, buttons, and fields as guidance. It does not describe authentication or rate limits, but with annotations covering safety, this is adequate.

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 description is front-loaded with the core idea, but it includes some unnecessary phrasing such as 'from ChatGPT, Claude or any AI agent' and a long final sentence about Uscreen's official API that is not essential for invoking the tool. The structure is understandable but could be tighter.

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 guide tool with no output schema, the description explains what is returned (step-by-step screens, buttons, fields) and what to do next (use cotlet_browser_* tools). It does not enumerate analytics categories, but the core behavior is sufficiently complete.

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 parameter semantics to explain. The baseline for a parameterless tool is 4, and the description does not need to compensate for missing schema details.

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 the resource (analytics in the user's Uscreen account) and clarifies that the tool returns step-by-step instructions rather than performing the action itself. It distinguishes itself from the cotlet_browser_* tools by saying it opens nothing and that those tools should be used afterward. The initial phrase 'Get analytics' is somewhat misleading, but the following sentence corrects it.

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 explicitly says to use this tool first to get step-by-step instructions, then use cotlet_browser_* tools in the Uscreen Cloud Browser to perform the action. It does not compare against other uscreen_* siblings or state when not to use it, but the primary workflow is clear.

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

All Uscreen MCP Server and API by Cotlet tools Inspect

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

Need Help?