Skip to main content
Glama
thenavidm

Kit MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Bulk create custom fields

bulk_create_custom_fields

Create multiple custom fields in a Kit account to organize subscriber data; requires OAuth and changes account configuration.

Instructions

Bulk create custom fields. Changes account configuration. Requires OAuth; API keys are not supported for this endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
callback_urlNo
payload_fileNoLocal JSON request body file, at most 5 MB. Contents are validated before the API call and are never logged.
custom_fieldsNo

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false. The description adds two things beyond that: the mutation alters account-level configuration, and the endpoint requires OAuth rather than API keys. That auth constraint is not derivable from annotations and is material for an agent planning a call.

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?

Three short sentences with the action front-loaded, then the side effect, then the auth constraint in descending order of importance. 'Changes account configuration' is close to redundant with the tool name but does flag the mutation, so it earns partial credit.

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?

No output schema exists, and the tool is a non-idempotent mutation with nested objects and five parameters. The description covers the mutation and auth surface adequately for its length but says nothing about partial-failure behavior on bulk creation or what the response returns, which is a real gap for a bulk write.

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 60% and the description supplies no parameter detail at all, including whether bulk creation takes the same shape as the singular variant. The schema's own descriptions of account, payload, and payload_file are decent, so the baseline 3 applies, but the description misses an opportunity to clarify the payload vs. body-flags vs. payload_file exclusivity that matters for a nested bulk tool.

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 ('bulk create custom fields') with the bulk scope made explicit, which distinguishes it from the singular create_custom_field sibling in the tool list. It does not name that sibling directly, so an agent must consult the list to confirm the split.

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

Usage Guidelines3/5

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

Provides a prerequisite (OAuth required, API keys unsupported) which is genuine usage context, but gives no when-to-use guidance and never contrasts with create_custom_field or bulk_update_subscriber_custom_field_values. The routing decision is left to inference.

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