Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update a custom field

update_custom_field

Modify an existing custom field's label and configuration in a Kit account by supplying the field ID and updated details.

Instructions

Update a custom field. Changes account configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNo
accountNoNamed private account from KIT_ACCOUNTS. Defaults to KIT_DEFAULT_ACCOUNT or the first configured account.
payloadNoComplete JSON body instead of individual body flags. Supports nullable fields and nested bulk structures. Cannot be combined with body flags or payload_file.
payload_fileNoLocal JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
custom_field_idYesPositive custom field id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true for audience/delivery changes, publishing, destructive operations and signing-secret changes. Use only for an action requested by the user.",
-  "type": "boolean"
-}
  2. First observedv2.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so safety basics are covered. The only added context is the vague note that it 'Changes account configuration', which doesn't explain what gets modified, whether updates are reversible, or permission requirements. Much more could be said for a mutation tool.

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?

Two short sentences with no filler; the purpose is front-loaded. However, the second sentence is low-information and could be removed without losing clarity, keeping it just shy of a 5.

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

Completeness2/5

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

The tool has 5 parameters, nested objects, and one required id, but the description omits any detail on partial vs. full updates, how payload interacts with individual body flags, or permission requirements. With no output schema and thin annotations, the description leaves substantial gaps for an agent to operate correctly.

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 80%, so the schema already documents account, payload, payload_file, and custom_field_id well. The description adds no parameter-level meaning beyond what is in the schema, which matches the baseline 3 when schema coverage is high.

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

Purpose4/5

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

States a specific verb+resource ('Update a custom field'), which is clear on its own and distinguishes the tool from siblings like create_custom_field, delete_custom_field, and bulk_update_subscriber_custom_field_values. The second sentence adds no additional purpose clarity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as bulk_update_subscriber_custom_field_values or create_custom_field. No prerequisites or conditions are stated, so an agent must infer usage entirely from the name and schema.

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

Deploy Server

Other Tools