Skip to main content
Glama
deyikong

SendGrid MCP Server

by deyikong

Create Custom Field

create_custom_field

Create a new custom field for your contacts to store additional data. Specify a name and field type (Text, Number, or Date).

Instructions

Create a new custom field for contacts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the custom field
field_typeYesType of the field

Implementation Reference

  • Handler function that creates a custom field by POSTing to SendGrid's field_definitions API with name and field_type
    handler: async ({ name, field_type }: { name: string; field_type: string }): Promise<ToolResult> => {
      const readOnlyCheck = checkReadOnlyMode();
      if (readOnlyCheck.blocked) {
        return { content: [{ type: "text", text: readOnlyCheck.message! }] };
      }
      
      const result = await makeRequest("https://api.sendgrid.com/v3/marketing/field_definitions", {
        method: "POST",
        body: JSON.stringify({ name, field_type }),
      });
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    },
  • Schema definition for create_custom_field tool with name (string) and field_type (enum: Text, Number, Date)
    config: {
      title: "Create Custom Field",
      description: "Create a new custom field for contacts",
      inputSchema: {
        name: z.string().describe("Name of the custom field"),
        field_type: z.enum(["Text", "Number", "Date"]).describe("Type of the field"),
      },
    },
  • Registration of create_custom_field as a property of contactTools object in src/tools/contacts.ts
    create_custom_field: {
      config: {
        title: "Create Custom Field",
        description: "Create a new custom field for contacts",
        inputSchema: {
          name: z.string().describe("Name of the custom field"),
          field_type: z.enum(["Text", "Number", "Date"]).describe("Type of the field"),
        },
      },
      handler: async ({ name, field_type }: { name: string; field_type: string }): Promise<ToolResult> => {
        const readOnlyCheck = checkReadOnlyMode();
        if (readOnlyCheck.blocked) {
          return { content: [{ type: "text", text: readOnlyCheck.message! }] };
        }
        
        const result = await makeRequest("https://api.sendgrid.com/v3/marketing/field_definitions", {
          method: "POST",
          body: JSON.stringify({ name, field_type }),
        });
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      },
    },
  • Re-export of contactTools (including create_custom_field) into the allTools aggregate
    export const allTools = {
      ...automationTools,
      ...campaignTools,
      ...contactTools,
      ...mailTools,
      ...miscTools,
      ...statsTools,
      ...templateTools,
    };
  • Help prompt mentioning create_custom_field as part of custom fields management tools
    Segments & Custom Fields:
    - list_segments: View segments with parent relationships
    - open_segment_creator: Open segment creator in browser
    - list_custom_fields: List custom field definitions
    - create_custom_field: Create new custom fields
    - update_custom_field: Update existing custom field definitions
    - delete_custom_field: Delete custom field definitions
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action without describing side effects, permissions required, or whether the operation is reversible. Minimal behavioral disclosure.

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

Conciseness3/5

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

Single sentence with 6 words, extremely concise. However, this brevity sacrifices useful information that could aid agent understanding. It is not verbose but may be under-specified.

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?

For a tool with 2 parameters and no output schema or annotations, the description is too minimal. It lacks context about field limits, uniqueness constraints, response format, and operational implications. Incomplete for reliable agent decision-making.

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 coverage is 100%, with both 'name' and 'field_type' described. The description adds no additional meaning beyond the schema; it merely paraphrases the action. Baseline score 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?

Description clearly states 'Create a new custom field for contacts', specifying verb (create), resource (custom field), and scope (for contacts). It effectively distinguishes from sibling tools like create_contact, update_custom_field, and delete_custom_field.

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. No prerequisites, exclusions, or context provided. The agent must infer appropriate usage from the name alone.

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/deyikong/sendgrid-mcp'

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