rename_view
Idempotent
Rename a view in an Airtable base by specifying the base ID, view ID, and the new name to assign.
Instructions
Rename a view.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| appId | Yes | The Airtable base/application ID | |
| viewId | Yes | The view ID to rename (e.g. "viwXXX") | |
| newName | Yes | The new name for the view | |
| debug | No | When true, include raw Airtable response in output for diagnostics |
Implementation Reference
- The AirtableClient method that sends the rename view request to Airtable's internal API endpoint /v0.3/view/{id}/updateName with payload { name, origin: 'viewName' }.
* Rename a view. * Real endpoint: /v0.3/view/{id}/updateName * Payload: { name: "...", origin: "viewName" } */ async renameView(appId, viewId, newName) { assertAirtableId(appId, 'appId'); assertAirtableId(viewId, 'viewId'); const url = `https://airtable.com/v0.3/view/${viewId}/updateName`; const payload = { name: newName, origin: 'viewName' }; const res = await this.auth.postForm(url, this._mutationParams(payload, appId), appId); if (!res.ok) { const errBody = await res.text().catch(() => ''); throw new Error(`renameView failed (${res.status}): ${errBody}`); } this.cache.invalidate(appId); return res.json(); } - The MCP tool handler function for 'rename_view' — it calls the AirtableClient.renameView method and returns the result.
async rename_view({ appId, viewId, newName, debug }) { const result = await client.renameView(appId, viewId, newName); return ok( { renamed: true, viewId, newName }, result, debug, ); }, - The schema definition for the 'rename_view' tool — specifies input parameters (appId, viewId, newName) and metadata.
{ name: 'rename_view', description: 'Rename a view.', annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false }, inputSchema: { type: 'object', properties: { appId: { type: 'string', description: 'The Airtable base/application ID' }, viewId: { type: 'string', description: 'The view ID to rename (e.g. "viwXXX")' }, newName: { type: 'string', description: 'The new name for the view' }, debug: debugProp, }, required: ['appId', 'viewId', 'newName'], }, }, - packages/mcp-server/src/tool-config.js:61-61 (registration)The tool is registered in TOOL_CATEGORIES under the 'view-write' category, which controls profile-based enable/disable.
rename_view: 'view-write', - Documentation/skill template entry describing rename_view tool usage.
| \`rename_view\` | Rename a view. |