Shootika

List styles

list_styles

Read-only

Lists the scene styles (backdrops and looks, plus the store's own reference scenes as ref:) a shoot can use: key, name, description and placement (true when the style also has a placement scene, for products shot alone). Use it with list_models to choose a scene. Returns every style in one result; takes no arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_styles"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive and closed-world, so the safety profile is covered. The description adds context the annotations cannot: the result is unpaginated ("returns every style in one result"), takes no arguments, and each entry carries key, name, description and placement, with placement flagged only for products shot alone.

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?

Two sentences, both load-bearing. The scope and ref:<id> convention come first, then the pairing guidance and result-shape facts. 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?

With no output schema, the description carries the burden of describing returns, and it does: field list, the placement flag's meaning, and the one-result cardinality. Only result ordering is unspecified, a minor gap for a small fixed list.

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?

The tool takes zero parameters, which sets the baseline at 4. The description reinforces this with "takes no arguments", leaving nothing ambiguous about invocation.

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 and resource (lists scene styles), then defines the domain precisely: backdrops and looks plus store reference scenes encoded as ref:<id>. That scope statement is enough to separate it from list_scenes and list_models without opening any schema.

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

Usage Guidelines4/5

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

"Use it with list_models to choose a scene" gives a concrete workflow pairing and the goal it serves. It stops short of explicitly excluding list_scenes, so an agent must still infer which of the two listing tools is the right entry point.

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

All Shootika tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?