Skip to main content
Glama

update_event

Update event details: name, date, description, tag, access code, album quality (pre-upload), download permissions, or collaborative upload settings. Only include the fields you want to change.

Instructions

Update fields on an existing event: name, event_date, description, tag, access_code, album_quality (storage resolution; changeable only before the first photo is uploaded, and tier-capped), enable_downloads (toggle guest downloads on/off), or is_collaborative (toggle whether other people can upload). Only include the fields you want to change. Use when the photographer wants to rename, re-date, re-code, change quality (pre-upload), or flip the downloads/collaborative toggles. If the photographer asks to change album_quality on an album that already has photos, the API will return a conflict error — relay that politely and explain they'd need to delete photos first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNo
nameNo
event_idYes
event_dateNoYYYY-MM-DD or null to clear
access_codeNo4-12 uppercase alphanumeric characters
descriptionNo
album_qualityNoStorage resolution. Changeable only before the first photo is uploaded; tier-capped.
enable_downloadsNoWhether guests can download photos.
is_collaborativeNoWhether other people can upload to this album.
Behavior5/5

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

No annotations are provided, but the description fully discloses behavioral traits: field constraints (album_quality changeable only pre-upload, tier-capped), toggling behavior for booleans, nullability for clearing values, and conflict errors.

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 thorough and well-structured, but slightly verbose. Every sentence adds value; no fluff, but could be tightened slightly without losing clarity.

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?

Given 9 parameters and no output schema, the description covers almost everything: parameter behavior, constraints, error scenarios. Missing only a note on what the API returns on success, but it's minor given the thoroughness.

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?

The description adds significant meaning beyond the schema, such as explaining album_quality constraints, toggle behavior for enable_downloads and is_collaborative, and error handling. Schema coverage is 56%, but description compensates fully.

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 clearly states 'Update fields on an existing event' and lists all modifiable fields, making the purpose explicit. It is distinct from sibling tools like create_event and delete_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 usage guidance: 'Only include the fields you want to change' and 'Use when the photographer wants to...'. Also includes a specific when-not scenario for album_quality and error handling advice.

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