Skip to main content
Glama

create_event

Create a new photo gallery event for weddings or occasions. Get event ID, access code, gallery link, and QR code.

Instructions

Create a new FindMe event (a wedding/photo gallery). Returns the event id, a shareable access code, and gallery + QR URLs. Use when the photographer says things like "create an event for Sarah & Mike on April 22" or "make a new gallery called Johnson Wedding". CRITICAL — three album settings are user preferences: album_quality (storage resolution; tier-capped), enable_downloads (guest downloads on/off), is_collaborative (others can upload). DO NOT guess, infer, or fill in defaults for these three fields yourself — you have no way to know what the photographer prefers. On the FIRST call, omit all three of these fields (only pass name + optional date/description/tag). The tool will respond with either an interactive form (clients with elicitation support) or a structured needs_input JSON listing tier-allowed options and recommended defaults — surface those options to the photographer as a numbered multiple-choice list, never as an open-ended question, and wait for their answer. Only then call create_event again with the photographer's chosen values. The only exception: if the photographer explicitly states a preference in their initial message (e.g. "make it collaborative" or "use 4000px quality"), you may include those specific stated preferences. FindMe has a playful, confident voice — when the event is created, give a short upbeat reaction that names the gallery and its access code, and mention the album_quality (e.g. "stored at 4000px, your plan's top setting"). Do not use the same phrasing twice. AFTER the album is created, if the photographer wants to add photos (e.g. they said "create an album and upload the photos in my Smith folder"), immediately call get_upload_link and hand them the link — tell them to tap it and pick their photos or their whole folder in the browser. You cannot read their local folder in this chat, so never ask for a file path; the folder/photos are chosen on the upload page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional tag/category (e.g. "wedding", "corporate").
nameYesEvent name, e.g. "Sarah & Mike Wedding"
event_dateNoEvent date in YYYY-MM-DD format. Optional.
descriptionNoOptional description.
album_qualityNoStorage resolution. Tier-capped — call without this and the tool will return your allowed options.
enable_downloadsNoWhether guests can download photos from the gallery.
is_collaborativeNoWhether the album is shareable/collaborative — other people can upload photos to it.
Behavior5/5

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

Reveals critical behavioral traits: returns interactive form or needs_input JSON, tier-capped album_quality, multi-step workflow, and post-creation photo upload guidance. Since no annotations exist, the description carries full burden and does so thoroughly.

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?

Well-structured with a clear flow, but notably long (multiple paragraphs). Each sentence serves a purpose, but some procedural details could be condensed without losing clarity. Still, it's well-organized and front-loaded.

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?

Comprehensive given the absence of output schema: describes return values (event id, access code, URLs). Covers the multi-step interaction for album settings and integration with upload workflow. No missing elements apparent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond schema by explaining that album_quality, enable_downloads, is_collaborative are user preferences not to be guessed, and provides the proper elicitation workflow. Schema already covers 100% of parameters with descriptions, but the tool description enriches their contextual usage.

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?

Clearly states it creates a new FindMe event (wedding/photo gallery) and specifies return values (event id, access code, URLs). Distinguished from sibling tools like get_event, update_event.

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?

Provides explicit when-to-use instructions (photographer requests to create an event), detailed step-by-step process for first call vs. subsequent calls, how to handle defaults, and when to include explicit preferences. Also advises calling get_upload_link after creation if photos are involved.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/findmephoto/findme-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server