Sunset Strip: GTA 6

Studio Pro

get_sunset_strip_pro

Read-only

Studio Pro, Sunset Strip's paid plan for GTA streamers and creators, including console streamers on PS5 and Xbox: "Build a channel worth watching. Know when to stream, what to create and how to grow." Returns what it includes (live controls for console streamers: clip, retitle and follow chat from your phone while you stream; Your Path with three missions a week, best time to stream, Trend Radar, title trends, raid finder, channel check, the Affiliate tracker, Twitch stats, competitor watch and Clip Autopilot), the current price (read from the Stripe price checkout charges; one monthly plan, no free trial), how to subscribe (a link that signs the user in and opens Stripe Checkout) and links to the plan page and Studio. Use it whenever a user wants help growing a GTA channel.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that the price is read from Stripe checkout charges, that there is one monthly plan with no free trial, and that the subscribe link signs the user in and opens Stripe Checkout. This adds useful behavioral context for a zero-parameter read tool, though it does not mention pagination, rate limits, or other operational constraints.

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

Conciseness2/5

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

The description is a long marketing-heavy block front-loaded with a tagline ('Build a channel worth watching...') before the functional purpose. The exhaustive feature parenthetical and single run-on sentence make it harder to scan, and not every phrase earns its place for an agent deciding whether to call the tool.

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?

Given the zero-parameter read-only shape and absence of an output schema, the description does explain what the tool returns: plan inclusions, current price, subscription path, and links. It is largely complete for calling the tool, though it lacks explicit disambiguation from feature-specific sibling tools.

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 the baseline is 4 and there are no parameters that require semantic clarification. The description appropriately focuses on return contents rather than input semantics.

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 clearly states the specific resource and verb: it returns Studio Pro plan inclusions, current price, subscription link, and related links. It is distinguishable as plan/pricing information rather than stream stats or trend data, though it does not explicitly name sibling tools or say what it does not return.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is limited to 'Use it whenever a user wants help growing a GTA channel,' which is broad and overlaps heavily with siblings like get_best_time_to_stream, get_trend_radar, and get_gta_twitch_stats. There are no when-not conditions, no alternatives, and no guidance to use this only for Studio Pro plan, pricing, or subscription questions.

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

All Sunset Strip: GTA 6 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?