Skip to main content
Glama

set_form_metadata

Idempotent

Update multiple form view metadata properties—like description, confirmation message, and redirect URL—in a single call without modifying other settings.

Instructions

Update one or more legacy-form-view metadata properties in a single call. Unset properties are not touched. Each property fans out to its own atomic Airtable endpoint.

Supported properties: description — intro text shown above the form afterSubmitMessage — "thank you" text after submission redirectUrl — URL to redirect to after submit refreshAfterSubmit — post-submit behavior (e.g. "REFRESH_BUTTON") shouldAllowRequestCopyOfResponse — boolean: show "send me a copy" toggle to respondents shouldAttributeResponses — boolean: track which user submitted (for signed-in respondents) isAirtableBrandingRemoved — boolean: hide Airtable branding (paid plans only)

Note: "form title" is the view name itself — use rename_view to change it. "Field labels on the form" use a per-field endpoint that has not been captured yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe Airtable base/application ID
viewIdYesThe form view ID
descriptionNoIntro text shown above the form (omit to leave unchanged)
afterSubmitMessageNoConfirmation text shown after submission
redirectUrlNoURL to redirect to after submit
refreshAfterSubmitNoPost-submit behavior (e.g. "REFRESH_BUTTON")
shouldAllowRequestCopyOfResponseNoAllow respondents to request a copy of their submission
shouldAttributeResponsesNoTrack which signed-in user submitted each response
isAirtableBrandingRemovedNoHide the Airtable branding on the form (paid plans)
debugNoWhen true, include raw Airtable response in output for diagnostics
Behavior4/5

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

Annotations provide idempotentHint=true, which the description does not contradict. The description adds transparency by noting that unset properties are untouched and that it fans out to atomic Airtable endpoints. This exceeds the baseline set by annotations.

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

Conciseness4/5

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

The description is front-loaded with the main action and then lists properties. It is reasonably concise but could be trimmed further since the properties are also described in the schema. No unnecessary sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers input details well but does not explain the output (no output schema). It omits error handling, response format, and prerequisites (e.g., must be a legacy form). Given the lack of output schema, this is a notable gap.

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?

Schema description coverage is 100%, so baseline is 3. The description lists supported properties with brief explanations that partially duplicate the schema. It adds marginal context (e.g., 'intro text shown above the form') but does not significantly enhance parameter understanding.

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 tool updates legacy-form-view metadata properties in a single call. It lists supported properties and distinguishes from sibling tools like rename_view for changing the form title, providing specific verb and resource.

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 explains when to use this tool (updating form metadata) and explicitly notes alternatives: rename_view for title changes and a per-field endpoint for field labels. It could be more explicit about not using it for non-form views, but the context is clear.

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