Skip to main content
Glama
thenavidm

Fourthwall MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set streaming status to started

start_streaming
Destructive

Sets streaming status to started for specified services, letting agents update a shop when a broadcast begins.

Instructions

Rate limit: 100 requests / 10 seconds per shop. See Rate limiting.

Sets streaming status to started for specified services

Input Schema

NameRequiredDescriptionDefault
accountNoExact private shop profile label; not a provider identity or authorization proof.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete current native JSON body; cannot mix with native body flags or payload_file.
servicesNo
payload_fileNoAbsolute regular non-symlink native JSON body file, at most1MiB. Cannot mix with payload or body flags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "services": {
+    "items": {
+      "oneOf": [
+        {
+          "allOf": [
+            {
+              "properties": {
+                "type": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "type"
+              ],
+              "title": "Service"
+            },
+            {
+              "properties": {
+                "broadcasterId": {
+                  "type": "string"
+                },
+                "broadcasterLogin": {
+                  "type": "string"
+                },
+                "thumbnailUrl": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            }
+          ],
+          "required": [
+            "broadcasterId",
+            "broadcasterLogin"
+          ],
+          "title": "Twitch"
+        }
+      ]
+    },
+    "type": "array"
+  }
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Explicit approval for this exact provider effect or local private-file operation."New value: +"Set true only when the user asked for exactly this action."
    • addedInput schema / properties / payload / properties / services / $ref
      Added value: +"#/$defs/services"
    • removedInput schema / properties / payload / properties / services / items
      Removed value: -{
-  "oneOf": [
-    {
-      "allOf": [
-        {
-          "properties": {
-            "type": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "type"
-          ],
-          "title": "Service"
-        },
-        {
-          "properties": {
-            "broadcasterId": {
-              "type": "string"
-            },
-            "broadcasterLogin": {
-              "type": "string"
-            },
-            "thumbnailUrl": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        }
-      ],
-      "required": [
-        "broadcasterId",
-        "broadcasterLogin"
-      ],
-      "title": "Twitch"
-    }
-  ]
-}
    • removedInput schema / properties / payload / properties / services / type
      Removed value: -"array"
    • addedInput schema / properties / services / $ref
      Added value: +"#/$defs/services"
    • removedInput schema / properties / services / items
      Removed value: -{
-  "oneOf": [
-    {
-      "allOf": [
-        {
-          "properties": {
-            "type": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "type"
-          ],
-          "title": "Service"
-        },
-        {
-          "properties": {
-            "broadcasterId": {
-              "type": "string"
-            },
-            "broadcasterLogin": {
-              "type": "string"
-            },
-            "thumbnailUrl": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        }
-      ],
-      "required": [
-        "broadcasterId",
-        "broadcasterLogin"
-      ],
-      "title": "Twitch"
-    }
-  ]
-}
    • removedInput schema / properties / services / type
      Removed value: -"array"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a concrete, non-annotation behavioral constraint: a 100 requests / 10 seconds per shop rate limit with a link to the rate-limiting guide. It still omits consequences of the action (e.g., what state change occurs for viewers), keeping it short of a 5.

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

Conciseness4/5

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

Two short sentences with no filler; the rate-limit note earns its place. Structure is slightly off since the caveat is front-loaded ahead of the actual purpose, pushing the verb to the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, zero-required, nested-object mutation with no output schema, the description covers purpose plus throttling but omits the lifecycle context an agent needs — that this begins an actual live broadcast, how it pairs with end_streaming, and how the payload/payload_file/body-flag alternatives relate. Annotations carry safety, so the gaps are moderate rather than severe.

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

Parameters3/5

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

Schema description coverage is 80%, so the schema already documents account, confirm, payload, payload_file, and the nested services shape. The description adds nothing about parameters — it does not explain the Twitch service object structure, the confirm flag semantics, or the mutually exclusive payload/body-flag modes.

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?

States a specific verb and resource: 'Sets streaming status to started for specified services.' An agent can distinguish this from end_streaming and get_streaming_status by the verb alone, but the description never names those siblings or clarifies the relationship in text.

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?

There is no when-to-use guidance at all — no mention of prerequisites, of when to prefer this over end_streaming/get_streaming_status, or of when starting a stream is inappropriate. 'For specified services' is scope, not usage guidance.

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

Deploy Server

Other Tools