Skip to main content
Glama

Show content on a screen

push_content
DestructiveIdempotent

Show content on one screen, or on one sub-screen of a split screen, in place of what it shows now, until a time or until it is put back to normal. A split screen needs a subscreen_id. Returns what the screen shows afterwards. Content only appears once the screen is online and has a player paired; the result includes online and paired when the connection may read screens.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "screen_id": "<screen_id>",
      "content_id": "<content_id>"
    },
    "name": "push_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
untilNoWhen to go back to normal: local time of the account without an offset (for example 2026-10-23T18:00), or a time with an offset (2026-10-23T18:00:00+02:00). At most 90 days ahead. Leave out to show it until it is put back to normal.
screen_idYesId of the screen, as listed with the team's screens.
content_idYesId of the file, design, app, split screen or playlist to show, as found in the team's content.
subscreen_idNoId of one sub-screen of a split screen. Required for a split screen, left out for a normal screen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / content_id / description
      Added value: +"Id of the file, design, app, split screen or playlist to show, as found in the team's content."
    • addedInput schema / properties / screen_id / description
      Added value: +"Id of the screen, as listed with the team's screens."
    • addedInput schema / properties / subscreen_id / description
      Added value: +"Id of one sub-screen of a split screen. Required for a split screen, left out for a normal screen."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare mutation, destructive, openWorld, and idempotent behavior. The description adds that current content is replaced until a time or reset, that content appears only once the screen is online and paired, and that the result may include online/paired; it does not cover permissions or failure behavior, but it adds substantive context beyond the annotations.

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?

The description is front-loaded with purpose and then adds split-screen, return-value, and prerequisite details in four sentences. Some phrasing such as 'when the connection may read screens' is slightly vague, but there is no filler.

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 destructive, open-world mutation with four parameters and no output schema, the description covers intent, replacement semantics, prerequisites, and return content. It leaves the revert workflow and permission details to siblings or external context, but annotations and schema cover safety and parameter details adequately.

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?

All four parameters have full schema descriptions, including the until time limit and the conditional subscreen_id requirement. The description reinforces the split-screen requirement but adds little else beyond what the schema already states, so the baseline score of 3 applies.

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

Purpose5/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: show content on one screen or one sub-screen of a split screen, replacing what it shows now. This clearly distinguishes it from release-type and activation siblings without requiring the schema.

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

Usage Guidelines3/5

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

It explains use for one screen or a split-screen sub-screen and notes that a split screen needs subscreen_id, but it gives no explicit when-not guidance or named alternatives such as release_screen for reverting. The conditions are implied rather than routing the agent between alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources