Skip to main content
Glama

Get a Look

get_look
Read-onlyIdempotent

One Look with its design and preview images backgrounds.portrait and backgrounds.landscape are the background plates the video uses; backgrounds.previews has 480 px wide copies of them for thumbnails (null for a Look without a photo or video background).

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": {
      "look_id": "<look_id>"
    },
    "name": "get_look"
  }
}

Input Schema

NameRequiredDescriptionDefault
look_idYesThe Look id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine value beyond that by disclosing the return shape: backgrounds.portrait/landscape hold full background plates while backgrounds.previews holds 480 px thumbnail copies, and explicitly notes previews is null when a Look has no photo/video background.

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

Conciseness3/5

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

It is short, but the prose is garbled: 'its design and preview images backgrounds.portrait and backgrounds.landscape' runs two ideas together with no punctuation, forcing the reader to re-parse which fields belong to which clause. The valuable null-behavior detail is buried in a trailing parenthesis rather than front-loaded.

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?

With no output schema, the description usefully explains the nested background fields, which is the most complex part of the response. However, it never mentions the top-level design/preview fields it advertises, nor error behavior for an invalid or unknown look_id, leaving the picture only partly complete.

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?

There is a single parameter (look_id) with 100% schema description coverage, so the schema already carries the semantics; the description adds nothing about format, source, or how to obtain a look_id. Baseline 3 applies when the schema does the work.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it returns 'One Look with its design and preview images', which identifies the resource and implies a single-item retrieval, but never states the verb ('retrieve/fetch a Look by id') and does nothing to distinguish it from siblings like list_looks, show_looks, or get_music_video_lookbook. An agent must infer that this is the by-id fetch.

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 explicit when-to-use guidance and no alternatives are named, despite the presence of several closely related siblings (list_looks, show_looks, get_music_video_lookbook, get_video). The reader is left to infer that a known look_id is the precondition.

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