All tools

excel_create

Documents · macOS · Windows

Effect: write (strongest supported action). Status: gated.

Gated means the tool requires an installed app, a connected account, permission, or runtime availability. Check those requirements on the listed platform before using it.

macOS

Purpose

Creates a new Excel spreadsheet (.xlsx file) with headers and optional data rows. JSON numbers (integers and decimals) are written as numbers, so SUM() and charts work on them; JSON strings always stay text even when they look numeric ("007", "1e3", or " 42"), as do integer values longer than 10 digits because they are identifiers like a CUIT, CBU or phone number rather than quantities.

Required inputs

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.

Full input schema — macOS
{
  "properties": {
    "confirm": {
      "description": "Must be true to create",
      "type": "boolean"
    },
    "headers": {
      "description": "Column headers",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "path": {
      "description": "Output path for the .xlsx file",
      "type": "string"
    },
    "rows": {
      "description": "Array of row arrays with data (optional)",
      "type": "array"
    }
  },
  "required": [
    "path",
    "headers"
  ],
  "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,
  "headers": [
    "Task",
    "Owner"
  ],
  "path": "/Users/demo/Documents/launch-checklist.xlsx"
}

Windows

Purpose

Creates a new Excel (.xlsx) file with headers and optional data rows.

Required inputs

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.

Full input schema — Windows
{
  "properties": {
    "confirm": {
      "description": "Must be true to create the file",
      "type": "boolean"
    },
    "headers": {
      "description": "Column headers",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "path": {
      "description": "Absolute path for the new .xlsx file",
      "type": "string"
    },
    "rows": {
      "description": "Data rows (array of arrays)",
      "items": {
        "items": {
          "type": "string"
        },
        "type": "array"
      },
      "type": "array"
    }
  },
  "required": [
    "path",
    "headers"
  ],
  "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,
  "headers": [
    "Task",
    "Owner"
  ],
  "path": "C:\\Users\\demo\\Documents\\launch-checklist.xlsx"
}