Skip to main content
Glama

Ver mídia de referência

designeer_media

Fetches high-resolution images and video stills from a Designeer find or listing to inspect layout, typography, and color references; files stay off disk by default, with optional motion frames.

Instructions

Puxa a mídia de um find ou listing do Designeer (imagens em alta, still do vídeo) e devolve as imagens pra você ENXERGAR a referência — layout, dashboard, tipografia, cor. Por padrão nada fica no disco. Para motion, peça frames > 0 (precisa de ffmpeg). Para ver a página de verdade de um site (ou uma tela dentro de uma galeria), use designeer_capture.

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": {
      "target": "<target>"
    },
    "name": "designeer_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoPasta destino quando save=true
saveNoGuardar os arquivos em ~/designeer-media (padrão: não guarda nada)
framesNoFrames extras de cada vídeo, pra entender o movimento (0 = só o still)
targetYesURL/path do find ou listing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose key behavior: nothing is written to disk by default, and requesting extra frames imposes an external dependency (ffmpeg). It stops short of covering error modes, size/rate limits, or exactly what the response payload looks like when save=true, so it is strong but not exhaustive.

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?

Three short sentences, each doing distinct work: what it fetches and returns, the default non-persistence, then the motion and capture alternatives. The core purpose and the sibling routing are front-loaded with 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?

There is no output schema, so the description must convey returns — it does so by framing the result as viewable images, which is the essential contract. It leaves open the concrete return shape (inline image data versus file paths, especially with save=true), which is the main remaining gap for a four-parameter tool.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by adding meaning the schema does not carry — the ffmpeg prerequisite for frames > 0 and the intent of frames as motion understanding. The dir parameter is left to the schema alone, which is acceptable given full coverage.

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 names a specific verb and resource — pulling media (high-res images, video still) from a Designeer find or listing — and states what the caller gets back (images to visually inspect the reference). It explicitly contrasts itself with designeer_capture, so an agent can distinguish it from a sibling without opening either schema.

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?

It gives concrete routing rules: use this to see the reference itself, set frames > 0 for motion, and switch to designeer_capture when you need the live page or a screen inside a gallery. Both the when-to-use and the when-to-use-something-else conditions are stated outright.

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