Skip to main content
Glama

Hide from public page

set_hidden
Idempotent

Leave one item off the user's public page (hidden = true), or let it show again (false). It stays in their library either way.

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": {
      "media_type": "<media_type>",
      "hidden": "<hidden>"
    },
    "name": "set_hidden"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoExact title of the item (or pass item_id)
hiddenYestrue to hide from the public page, false to show
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
media_typeYesType of media

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructiveHint=false, but the description adds genuinely useful scope information: the item remains in the library either way, so the effect is confined to public-page visibility rather than deletion. It does not cover failure behavior for an unmatched title or id, or whether anything is returned.

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 short sentences, no filler, with the primary effect stated first and the reassuring non-destructive consequence second. Every clause is load-bearing.

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 simple boolean toggle with full schema coverage, explicit annotations, and no output schema, the description covers effect, reversibility, and blast radius. Only edge behavior (item not found, ambiguous title) is left unexplained, which is a minor gap at this complexity level.

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%, including the meaning of hidden and the title-vs-item_id precedence, so the schema carries the parameter burden. The description's restatement of hidden=true/false adds only a little reinforcement and says nothing about media_type or the title/item_id choice.

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 concrete verb and resource: it makes one item not appear on the user's public page, and can reverse that. An agent can picture the effect without opening the schema. It does not, however, distinguish this from nearby siblings such as pin_to_page/unpin_from_page or show_item, which also affect what appears on the page.

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

Usage Guidelines3/5

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

Guidance is limited to the boolean semantics (true hides, false shows), which is closer to parameter explanation than routing advice. There is no statement of when to prefer this over pin_to_page, set_page_sections, or style_page, and no exclusions or prerequisites are given.

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