Skip to main content
Glama

Kubeez

view_media

Read-onlyIdempotent

Scope: read:generations. Return one of YOUR generated outputs as inline media, so it is displayed rather than linked. Pass output_id — the id inside outputs[] from get_status / get_generation / get_generations (the OUTPUT id, not the generation id). USE THIS when you want the user to actually SEE an image you just made, and ALWAYS instead of downloading media.kubeez.com yourself: many hosts block that origin in their sandbox, and fetching it externally wastes a turn and a second copy of the file. Images and audio come back as inline media. Video, anything over the 3.5 MiB inline limit, and any CDN failure come back as a short text pointer to the URL instead — MCP has no inline video block. Owner-only: another user's output is refused.

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": {
      "output_id": "<output_id>"
    },
    "name": "view_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Goes well beyond the annotations, which only declare read-only/idempotent/non-destructive. It discloses the required scope (read:generations), the 3.5 MiB inline cap, that video cannot be returned inline because MCP has no video block, that CDN failures and oversize items degrade to a text URL pointer, and that other users' outputs are refused.

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

Conciseness5/5

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

Front-loads the scope, then the argument, then the usage directive, then the return/failure behavior. Dense but every clause carries decision-relevant information; no filler or repetition of the annotations.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing exactly what comes back in each case (inline image/audio, text pointer for video, oversize, or CDN failure) along with the ownership restriction. Nothing an agent needs to invoke or interpret this tool is missing.

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

Parameters5/5

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

Schema coverage is 0% for the single parameter, so the description carries the full burden and does: it specifies that output_id is the id inside outputs[] from get_status / get_generation / get_generations, and explicitly warns it is the OUTPUT id, not the generation id — the one ambiguity that would otherwise cause wrong calls.

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?

States a specific verb-resource pair: return one of the caller's generated outputs as inline media so it is displayed rather than linked. It immediately distinguishes itself from the id-based metadata siblings (get_status / get_generation / get_generations) by naming them as the source of the id, not a substitute.

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

Usage Guidelines5/5

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

Explicit when-to-use ("USE THIS when you want the user to actually SEE an image you just made") plus an explicit instruction to always prefer it over downloading media.kubeez.com directly, with the reason given (host sandbox blocking, wasted turn). It also routes the agent to the sibling tools that supply the id argument.

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