Skip to main content
Glama

Publish or unpublish a Look

set_look_visibility
Idempotent

Make one of your Looks public (earns 10 credits) or private Public Looks join the Community library under your @username. A Look that shows your artist stays private (409).

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>",
      "visibility": "<visibility>"
    },
    "name": "set_look_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
look_idYesThe Look id
visibilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare mutation safety, idempotency, and open-world behavior. The description adds meaningful consequences beyond that: public Looks cost/earn 10 credits, join the Community library under your @username, and the 409 constraint for artist Looks.

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

Conciseness4/5

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

The description is two sentences and front-loads the core action and consequences. There is minor awkwardness in phrasing, but every sentence contributes useful information.

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?

For a mutation tool with annotations covering safety and idempotency, the description supplies the key operational context: credit effect, publication destination, and the 409 restriction. It is largely complete, though it could mention visibility semantics more explicitly.

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 coverage is 50%, with look_id documented and visibility only having an enum. The description adds semantic meaning to the visibility parameter by explaining the effects of public vs. private, but it does not add detail about look_id or otherwise compensate fully for the coverage gap.

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 states a specific verb and resource: making a Look public or private. It is clearly distinguishable from siblings such as rename_look, delete_look, and get_look by its publishing action.

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?

It implies when to use the tool (publishing/unpublishing) and gives an explicit exclusion: a Look showing your artist stays private and returns 409. It does not name alternative tools, but the usage context is clear enough.

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