Skip to main content
Glama

Hide products

hide_products
Idempotent

Use when the venue owner asks to remove, hide or take products off their own menu. Products are hidden from the public menu, not deleted, and can be shown again with update_products (available: true) or undo_change. Identify products by product_id from get_my_menu. Up to 50 per call. Two steps: preview without confirm, then confirm: true after the owner agrees. Requires the owner to connect their PRENOTO account.

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": {
      "product_ids": "<product_ids>"
    },
    "name": "hide_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse or omitted: preview only. true: hide, only after the owner agreed.
venue_idNoOptional. Only needed when the account manages several venues (see list_my_venues).
product_idsYesFrom get_my_menu.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare non-read-only, non-destructive, idempotent. The description adds substantially more: the effect is hiding rather than deletion, the change is reversible via two named routes, there is a 50-item per-call ceiling, and there is a two-phase preview/confirm gate plus an auth prerequisite.

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?

Five short sentences, each carrying distinct information: trigger, side effect, reversibility path, id resolution, batch limit, and workflow. The key constraint (hide, not delete) is front-loaded before operational detail.

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 mutation tool with no output schema, everything an agent needs is present: how to identify targets, the preview/confirm protocol, the per-call cap, auth requirement, and how to reverse the action. No material gap remains.

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 product_ids, confirm and venue_id are already documented in the schema, including the preview-versus-confirm semantics. The description mostly reinforces those same points rather than adding new parameter meaning, so the baseline 3 applies.

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 concrete verb and resource (hide products on the owner's own menu) and immediately distinguishes it from deletion: 'hidden from the public menu, not deleted'. An agent can separate it from update_products and undo_change 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 Guidelines5/5

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

Gives the triggering condition ('venue owner asks to remove, hide or take products off their own menu'), names the recovery alternatives (update_products with available: true, or undo_change), and specifies the required PRENOTO account connection. It also prescribes the two-step sequence, preview then confirm after the owner agrees.

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