Skip to main content
Glama

rename_record_template

Idempotent

Rename a record template in an Airtable base by specifying the base ID, template ID, and new name.

Instructions

Rename an existing record template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe Airtable base/application ID
templateIdYesThe template ID (rtpXXX)
nameYesNew template name
debugNoWhen true, include raw Airtable response in output for diagnostics

Implementation Reference

  • The actual handler function for the rename_record_template tool. It calls client.renameRowTemplate() and returns the result.
    async rename_record_template({ appId, templateId, name, debug }) {
      const result = await client.renameRowTemplate(appId, templateId, name);
      return ok({ updated: true, templateId, name }, result, debug);
    },
  • Input schema definition for rename_record_template (name, description, inputSchema with appId, templateId, name, debug).
    {
      name: 'rename_record_template',
      description: 'Rename an existing record template.',
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          appId:       { type: 'string', description: 'The Airtable base/application ID' },
          templateId:  { type: 'string', description: 'The template ID (rtpXXX)' },
          name:        { type: 'string', description: 'New template name' },
          debug:       debugProp,
        },
        required: ['appId', 'templateId', 'name'],
      },
    },
  • The client-side implementation renameRowTemplate() that sends POST to /v0.3/rowTemplate/{templateId}/updateName.
    async renameRowTemplate(appId, templateId, name) {
      assertAirtableId(appId, 'appId');
      const url = `https://airtable.com/v0.3/rowTemplate/${templateId}/updateName`;
      const res = await this.auth.postForm(url, this._mutationParams({ name }, appId), appId);
      if (!res.ok) {
        const errBody = await res.text().catch(() => '');
        throw new Error(`renameRowTemplate failed (${res.status}): ${errBody}`);
      }
      return res.json();
    }
  • Tool category registration mapping rename_record_template to 'table-write' category.
    rename_record_template:              'table-write',
  • Extension-side tool profile registration mapping rename_record_template to 'table-write' category.
    rename_record_template:              'table-write',
Behavior4/5

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

Annotations already provide idempotency and non-destructiveness. The description accurately indicates a write operation (rename) without contradicting annotations. It doesn't add behavioral context beyond the annotations, but that is acceptable since annotations are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the essential information: the verb and resource. There is no wasted text or unnecessary detail.

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?

The description covers the main purpose adequately. Given the simple nature of a rename operation and the presence of annotations providing behavioral hints, the description is mostly complete. It could mention that only the name is changed and not the template content, but this is not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes all 4 parameters (appId, templateId, name, debug) with 100% coverage. The description adds no additional meaning or constraints beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action (rename) and resource (existing record template). It effectively distinguishes from sibling tools like create_record_template, delete_record_template, and duplicate_record_template, as well as other rename tools (rename_field, rename_table).

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

Usage Guidelines4/5

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

The description implies usage by naming the action, but does not explicitly state when to use this tool versus alternatives or when not to use it. However, the purpose is clear enough given the tool name and sibling tools, so no guidance is needed beyond the description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Automations-Project/VSCode-Airtable-Formula'

If you have feedback or need assistance with the MCP directory API, please join our Discord server