shortcuts_run

macOS

Purpose

Runs one of the user's macOS Shortcuts (Atajos) by name or identifier — the way Mac users already automate HomeKit, Focus modes, and third-party app actions the catalog doesn't cover. It runs the shortcut's OWN actions under the shortcut's own permissions, not a sandboxed subset — the same as clicking Run in the Shortcuts app. This is a write operation: the first call (confirm=false) returns a preview naming the shortcut, its identifier, and its folder, without running anything; set confirm=true to actually run it. A name that matches more than one shortcut is refused with both identifiers — call again with one of those, never guessed. A shortcut that waits on a dialog or runs long is stopped after a bounded timeout with a clear message instead of hanging this call.

Required inputs

• name_or_identifier — Shortcut name or identifier, from shortcuts_list. An ambiguous name is refused — pass the identifier instead.

Permissions and confirmation

Explicit confirmation parameter: inspect the schema and tool description before any real call. The documentation example keeps confirm false. Obtain user authorization before performing the action.

• Use only the apps, accounts and resources authorized by the user on this platform. Consult this tool's platform-specific description for its connection and permission requirements; this catalog does not assert additional OAuth scopes or OS entitlements.

{
  "properties": {
    "confirm": {
      "description": "Must be true to actually run the shortcut. Without it, returns a preview.",
      "type": "boolean"
    },
    "input_text": {
      "description": "Optional text input for the shortcut, passed via a temp file — omit if the shortcut takes no input.",
      "type": "string"
    },
    "name_or_identifier": {
      "description": "Shortcut name or identifier, from shortcuts_list. An ambiguous name is refused — pass the identifier instead.",
      "type": "string"
    }
  },
  "required": [
    "name_or_identifier"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "confirm": false,
  "name_or_identifier": "Demo morning brief"
}