rename-table

Rename a Data Table. Needs the fabric:table.write grant.

curl -sS -X POST https://fabric.wexa.ai/mcp/$FABRIC_PROJECT_ID \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "Mcp-Session-Id: $MCP_SESSION_ID" \
  -H "content-type: application/json" -H "accept: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"rename-table","arguments":{"table_id":"6ab196817566f41b5c28e31f","table_name":"docs_fixture_scratch_renamed"}}}'

{
  "content": [
    {
      "type": "text",
      "text": "{\"lifecycle_id\":\"qlc_000202\",\"result\":{\"table_id\":\"6ab196817566f41b5c28e31f\",\"table_name\":\"docs_fixture_scratch_renamed\",\"triggers_preserved\":0}}"
    }
  ],
  "isError": false
}

curl -sS https://fabric.wexa.ai/v1/rename-table \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "content-type: application/json" \
  -d '{"table_id":"6ab196817566f41b5c28e31f","table_name":"docs_fixture_scratch_renamed"}'

{
  "lifecycle_id": "qlc_000202",
  "result": {
    "table_id": "6ab196817566f41b5c28e31f",
    "table_name": "docs_fixture_scratch_renamed",
    "triggers_preserved": 0
  }
}

import { Fabric } from '@wexa-fabric/sdk'

const fabric = new Fabric()
const result = await fabric.renameTable({
  table_id: '6ab196817566f41b5c28e31f',
  table_name: 'docs_fixture_scratch_renamed'
})

// result is the payload itself, with no `.result` to read
{
  table_id: '6ab196817566f41b5c28e31f',
  table_name: 'docs_fixture_scratch_renamed',
  triggers_preserved: 0
}

from wexa import Fabric

fabric = Fabric()
out = fabric.rename_table(
    table_id="6ab196817566f41b5c28e31f",
    table_name="docs_fixture_scratch_renamed",
)

# out is the result, already unwrapped
{
    "table_id": "6ab196817566f41b5c28e31f",
    "table_name": "docs_fixture_scratch_renamed",
    "triggers_preserved": 0
}

Parameters

Parameter	Type	Required	Notes
`table_id`	string	Required	Table id from `list-tables`, a 24-character hex id. A table in this project.
`table_name`	string	Required	New name. Non-empty.

Show full response

A real response, captured from a live call to rename-table:

{
  "lifecycle_id": "qlc_000202",
  "result": {
    "table_id": "6ab196817566f41b5c28e31f",
    "table_name": "docs_fixture_scratch_renamed",
    "triggers_preserved": 0
  }
}

// the object you get back IS the result — there is no `.result` to read
{
  table_id: '6ab196817566f41b5c28e31f',
  table_name: 'docs_fixture_scratch_renamed',
  triggers_preserved: 0
}

// The TS SDK names these camelCase — lifecycleId, traceId — where Python uses
// lifecycle_id and trace_id. Both are non-enumerable: readable, but omitted by
// Object.keys() and JSON.stringify(). `result.lifecycleId` here is undefined.
result.lifecycleId // 'qlc_000202'

# a dict subclass; `result` is already unwrapped
{
 "table_id": "6ab196817566f41b5c28e31f",
 "table_name": "docs_fixture_scratch_renamed",
 "triggers_preserved": 0
}

out.lifecycle_id  # 'qlc_000202' — an attribute, not a key

More details

The table's triggers are read back and written with the new name, so renaming never disables the table's automation. The result reports triggers_preserved.

Every tool call works the same way: How every tool call works.