skylight-mcp

skylight_upload_photo

Destructive

Upload a photo or video to a Skylight frame slideshow: signs an S3 upload, registers it as a frame message, and asks for confirmation before anything is read or sent.

Instructions

Upload a photo or video from a local file to the Skylight frame (it appears in the slideshow). Two-step: signs an S3 upload with temporary credentials, then registers it as a frame message. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The preview echoes the resolved absolute image_path, detected mime, size and caption, and nothing is read or uploaded until it is confirmed.

Input Schema

TableJSON Schema

Name	Required	Description
`caption`	No	Caption shown with the photo.
`frameId`	No
`frame_ids`	No	Frame ids to post to; defaults to the resolved frame.
`image_path`	Yes	Absolute path to a local image/video file inside the upload directories (SKYLIGHT_UPLOAD_DIR; by default ~/Pictures and ~/Downloads) (jpg, jpeg, png, heic, gif, webp, mp4, mov; max 200 MiB). Anything else — a file outside those directories, a hidden file, a symlink, or a file whose contents do not match its extension — is refused.
`confirmToken`	No	ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.3.1Oct 3, 2026

changedInput schema / properties / image_path / description

Previous value: -"Absolute path to a local image/video file (jpg, jpeg, png, heic, gif, webp, mp4, mov; max 200 MiB). Anything else — or a symlink, or a file whose contents do not match its extension — is refused."New value: +"Absolute path to a local image/video file inside the upload directories (SKYLIGHT_UPLOAD_DIR; by default ~/Pictures and ~/Downloads) (jpg, jpeg, png, heic, gif, webp, mp4, mov; max 200 MiB). Anything else — a file outside those directories, a hidden file, a symlink, or a file whose contents do not match its extension — is refused."

Changed2 schema fields changedv1.3.0Sep 25, 2026

removedInput schema / properties / confirm

Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}

addedInput schema / properties / confirmToken

Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}

Changed1 schema field changedv1.1.3Sep 24, 2026

changedInput schema / properties / image_path / description

Previous value: -"Absolute path to a local image/video file (jpg, png, heic, mp4, …)."New value: +"Absolute path to a local image/video file (jpg, jpeg, png, heic, gif, webp, mp4, mov; max 200 MiB). Anything else — or a symlink, or a file whose contents do not match its extension — is refused."

Changed1 schema field changedv1.0.1Sep 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv0.7.1Aug 29, 2026
- removedInput schema / properties / frame_ids / items / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / frame_ids / items / type
```
Added value: +[
+  "string",
+  "number"
+]
```
First observedv0.4.6Jul 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it explains the two-phase confirmation mechanism, what the preview echoes, that nothing is uploaded until confirmed, and the fallback token flow. Annotations already flag it as a write/destructive operation; the description goes further in clarifying the safety flow.

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 a single dense paragraph that is well-structured and front-loaded with the main action, then the two-step process, then the confirmation mode. It is somewhat long but every sentence earns its place by covering the confirmation flow.

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 the destructive nature (annotations), the complex two-step confirmation, and the absence of an output schema, the description provides all the necessary context for an agent to call the tool correctly, including the preview behavior and the token fallback.

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?

The description meaningfully complements the schema by explaining the confirmToken's role and the preview details. The schema already documents image_path constraints and frame_ids, so the description does not need to repeat them. It adds value by describing the token's lifecycle and the preview's contents.

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 ('Upload a photo or video from a local file to the Skylight frame') and immediately clarifies the effect ('it appears in the slideshow'). It also outlines the two-step mechanics, which distinguishes it from all siblings.

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

Usage Guidelines4/5

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

It clearly explains the two-step confirmation flow and when to pass confirmToken, and notes that the token should only be used after explicit user approval. It does not, however, explicitly compare against sibling tools like skylight_add_to_album or skylight_copy_messages_to_frames.

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

Deploy Server

skylight_upload_photo

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools