skylight-mcp

skylight_copy_messages_to_frames

Copy messages or photos from a Skylight frame to multiple destination frames on the same account. Use message IDs and target frame IDs to transfer content.

Instructions

Copy messages/photos from this frame to other frames on the account (inferred from the app bundle, not live-verified).

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": {
      "message_ids": "<message_ids>",
      "new_frame_ids": "<new_frame_ids>"
    },
    "name": "skylight_copy_messages_to_frames"
  }
}

Input Schema

Name	Required	Description
`frameId`	No
`message_ids`	Yes	Message/photo ids to copy.
`new_frame_ids`	Yes	Destination frame ids (see skylight_list_frames).

Schema Changelog

Changes observed during successful MCP inspections.

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"

Changed4 schema fields changedv0.7.1Aug 29, 2026
- removedInput schema / properties / message_ids / items / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / message_ids / items / type
```
Added value: +[
+  "string",
+  "number"
+]
```
- removedInput schema / properties / new_frame_ids / items / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / new_frame_ids / items / type
```
Added value: +[
+  "string",
+  "number"
+]
```
Addedv0.5.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, open-world write operation, and the description is consistent with that. The parenthetical '(inferred from the app bundle, not live-verified)' is a genuinely useful reliability caveat, but the description says nothing about whether the source messages are retained, whether copies duplicate, idempotency, or permission requirements.

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?

One front-loaded sentence that states the action before the caveat; nothing is redundant. The parenthetical costs words but earns them by flagging unverified behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter, non-destructive write tool with no output schema, the description covers the core action but omits return/result behavior, what happens if a destination frame id is invalid, and how source frame resolution works. The 'not live-verified' note is honest but leaves the agent with unresolved behavioral questions.

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 coverage is 67%, so the schema documents message_ids and new_frame_ids while frameId is undocumented. The description's 'from this frame to other frames' adds a little meaning to the source/destination split, but does not explain the frameId parameter or the accepted id formats.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (copy) with the source resource (messages/photos in a frame) and destination (other frames on the account), so the agent can distinguish it from sibling tools like add_to_album or delete_messages. The phrasing is clear, though 'this frame' is only resolved via the frameId parameter rather than named explicitly.

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

Usage Guidelines2/5

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

The description gives no conditions for when to use this tool versus alternatives; it never mentions related siblings such as add_to_album, upload_photo, or delete_messages, nor any prerequisites. Usage is only implied by the frame-to-frame framing.

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

Deploy Server