Skip to main content
Glama

Open photo booth

open_photo_booth
Read-onlyIdempotent

Use this when the user wants a photo booth, selfie booth or "Fotobox" for a party, wedding, birthday, office party or any event, or wants to take fun group photos with effects on a phone, tablet or laptop. Shows a card with example images of all effects where the user picks an effect, a collage layout and an optional caption, then opens the browser photo booth with those settings in a new tab (no signup, no app; photos stay on the device). Also returns how it works and effect suggestions for the occasion. The booth cannot take photos inside the chat. Do not use for editing existing photos or for collecting photos from guests (use collect_guest_photos_info for that).

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": "open_photo_booth"
  }
}

Input Schema

NameRequiredDescriptionDefault
effectNoEffect the user asked for, if any. It is preselected in the card and the booth link.
layoutNoCollage layout the user asked for, if any: "square" (2×2), "column" (photo strip), "postcard", "instant" (instant-photo frame) or "feed" (social post). Defaults to "square".
captionNoShort caption for the bottom of the collage if the user gave one, e.g. names and date ("Emma & Noah · 12.06."). Max 40 characters are used.
languageNoLanguage of the booth: "de" for German-speaking users, "en" otherwise. Match the language of the conversation.
occasionNoOccasion in a few words, e.g. "wedding", "birthday", "office party", "Halloween". Used only to suggest effects.

Output Schema

NameRequiredDescriptionDefault
urlYes
brandYes
stepsYes
effectYes
layoutYes
captionYes
effectsYes
layoutsYes
boothUrlYes
languageYes
captionMaxYes
effectLabelYes
suggestedEffectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / layout / description
      Previous value: -"Collage layout the user asked for, if any: \"square\" (2×2), \"column\" (photo strip) or \"postcard\". Defaults to \"square\"."New value: +"Collage layout the user asked for, if any: \"square\" (2×2), \"column\" (photo strip), \"postcard\", \"instant\" (instant-photo frame) or \"feed\" (social post). Defaults to \"square\"."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description explains the user flow: a card with effect examples, user selection, then opening the booth in a new tab. It also discloses important limits and behavior: no signup, no app, photos stay on the device, the booth cannot take photos inside chat, and the tool returns how-it-works information and occasion-based effect suggestions.

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 primary use case and then adds only decision-relevant details such as the card flow, new-tab behavior, device-local photos, and exclusions. Despite its length, every sentence carries useful information for selecting and invoking this tool correctly.

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?

Given five optional parameters, annotations, and an output schema, the description covers the full user-facing flow and the important constraints an agent needs. Return-value details are supported by the output schema, while the description supplies the behavioral context that structured fields do not carry.

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?

Even though the schema has 100% description coverage, the description adds useful meaning: effects are preselected in the card and link, layout defaults to square, language should match the conversation, and occasion is used only for effect suggestions. One inconsistency lowers the score: the description says the caption uses max 40 characters while the schema allows maxLength 80.

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: it opens a browser-based photo booth after the user selects an effect, layout, and optional caption. It clearly distinguishes the tool from photo editing and guest-photo collection, and the sibling alternatives are named or implied.

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 gives explicit when-to-use triggers such as parties, weddings, birthdays, office parties, and fun group photos, plus when-not-to-use guidance for editing existing photos or collecting guest photos. The named alternative collect_guest_photos_info makes the routing decision clear.

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