Skip to main content
Glama

Show in Shoot Board

show_in_shoot_board
Idempotent

Moves a Shoot Board that is open in a widget to a view (board, brief, automation, results, brief_history). This client shows no widget, so it changes nothing the user sees: read the board, brief or results with read_shoot_board, get_brief or get_generation_results and tell the user.

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": {
      "view": "<view>",
      "board_id": "<board_id>"
    },
    "name": "show_in_shoot_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYesboard: the board's photos (Clothing, Models, Locations, references, the pinned Automation); brief: the brief's looks beside its automation (once it ran, each look with its photos and videos); automation: the same page, for its automation; results: a brief that ran, at its photos and videos; brief_history: every brief the user ran
board_idYesThe open Shoot Board's board_id, from Open Shoot Board or your context.
look_keyNobrief / results: the look to bring forward (a key of the brief's looks)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds an important behavioral caveat that the effect is invisible in this client, supplementing the annotations well. It does not describe return values, but the annotations already cover the safety profile, so this is a strong addition.

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?

The description is front-loaded with the core action, then immediately delivers the critical caveat and the recommended workaround. It is compact with no redundant sentences.

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?

For a three-parameter tool with full schema coverage and no output schema, the description provides the essential context an agent needs: what it does, where it has no visible effect, and what to do instead. Nothing critical is missing.

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 100%, so the schema already documents all parameters including the view enum and look_key pattern. The description adds no syntax or format details beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description states a specific action (move a Shoot Board that is open in a widget) and the target views, so the purpose is clear. It distinguishes itself from siblings by naming the read alternatives (read_shoot_board, get_brief, get_generation_results), but the underlying resource and effect are less immediately obvious than a tool like 'update_brief'.

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 explicitly tells the agent when not to bother: this client shows no widget, so the tool changes nothing visible, and instead the agent should read with read_shoot_board, get_brief, or get_generation_results. That is a concrete when/when-not with named 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