home-screen-mcp

Overview Schema Source Related Servers Discussions Admin

move

Rearrange iPhone or iPad Home Screen items by placing an app, widget, or folder in the Dock, App Library, a specific page, or folder, at a chosen index or before another item.

Instructions

Move one item to target ('dock', 'library', 'page:N', 'folder:[:N]'), at index (0-based, default end) or just before the item with id before. 'library' = App Library only, off the Home Screen.

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": {
      "item_id": "<item_id>",
      "target": "<target>"
    },
    "name": "move"
  }
}

Input Schema

Name	Required	Description	Default
`index`	No
`before`	No
`target`	Yes
`item_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that index is 0-based and defaults to the end, that 'before' takes an item id, and that 'library' means App Library only (off the Home Screen). It does not say whether items shift after the move, what happens on out-of-range index or unknown id, or whether the operation is reversible.

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?

Two dense sentences with the target grammar front-loaded and the placement rules following. No filler, though the parenthetical syntax is terse enough to require re-reading.

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?

An output schema exists, so return values need not be described. For a 4-param mutation with no annotations and no schema descriptions, the description covers destination grammar and placement semantics well; the remaining gap is item_id meaning and failure behavior.

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?

Schema coverage is 0%, so the description must compensate, and it does for three of four parameters: target's allowed value grammar, index's 0-based/default-end semantics, and before's meaning. Only item_id is left unexplained, though 'one item' implies it.

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 (move) and resource (one item) and enumerates the legal target forms ('dock', 'library', 'page:N', 'folder:<id>[:N]'). This is enough to tell it apart from siblings like swap, arrange or place_at, though it never explicitly contrasts with them.

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

Usage Guidelines3/5

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

It defines how to address a destination and the two placement modes (index vs. before), which implies its use case. However, it gives no explicit when-to-use guidance relative to the many sibling move/arrange tools, and no exclusions or prerequisites.

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