Skip to main content
Glama

delete_option_of_custom_field

DestructiveIdempotent

Delete a specific option from a custom field by providing the parent resource ID, field slug, and option ID.

Instructions

Delete an option from custom field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYesID of the parent resource
field_slugYesID of the parent resource
idYesID of the custom field option to delete

Implementation Reference

  • Handler function that executes the delete_option_of_custom_field tool logic. Calls apiDelete on `/custom/${object_type}/fields/${field_slug}/options/${option_id}`.
    async ({ object_type, field_slug, id }) => {
      try {
        const record = await apiDelete<EduframeRecord>(
          `/custom/${object_type}/fields/${field_slug}/options/${option_id}`,
        );
        void logResponse("delete_option_of_custom_field", { object_type, field_slug, id }, record);
        return formatDelete(record, "custom field option");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for the delete_option_of_custom_field tool. Expects object_type, field_slug, and id (all positive integers).
    inputSchema: {
      object_type: z.number().int().positive().describe("ID of the parent resource"),
      field_slug: z.number().int().positive().describe("ID of the parent resource"),
      id: z.number().int().positive().describe("ID of the custom field option to delete"),
    },
  • Registration of the tool via server.registerTool('delete_option_of_custom_field', ...) inside registerCustomFieldOptionTools.
    server.registerTool(
      "delete_option_of_custom_field",
      {
        description: "Delete an option from custom field",
        annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
        inputSchema: {
          object_type: z.number().int().positive().describe("ID of the parent resource"),
          field_slug: z.number().int().positive().describe("ID of the parent resource"),
          id: z.number().int().positive().describe("ID of the custom field option to delete"),
        },
      },
      async ({ object_type, field_slug, id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(
            `/custom/${object_type}/fields/${field_slug}/options/${option_id}`,
          );
          void logResponse("delete_option_of_custom_field", { object_type, field_slug, id }, record);
          return formatDelete(record, "custom field option");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • registerAllTools iterates all tool registrations, including registerCustomFieldOptionTools which registers this tool.
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
      }
    }
Behavior3/5

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

Annotations already provide destructiveHint=true and idempotentHint=true, indicating a safe-to-retry delete operation. The description adds no further behavioral insights (e.g., what gets deleted, cascading effects, permissions). It does not contradict annotations, so a baseline score is appropriate.

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?

The description is very concise (one phrase), but it lacks structured details. For a delete tool, brevity is acceptable, but the missing parameter context and usage guidance make it under-specified. It is not wasteful, but it could be more informative in the same space.

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?

Given the tool's destructive nature, three parameters, and no output schema, the description is insufficient. It does not explain how 'object_type' and 'field_slug' identify the custom field, nor does it address potential impacts or expected behavior. The description relies too heavily on the schema, which itself is incomplete.

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

Parameters2/5

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

Although schema coverage is 100%, the descriptions for 'object_type' and 'field_slug' are identical and vague ('ID of the parent resource'), failing to distinguish which resources they refer to. The tool description does not clarify these parameters. The 'id' param description is clear, but overall the semantic burden is not met.

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?

The description 'Delete an option from custom field' clearly specifies a verb ('Delete') and resource ('option from custom field'). It effectively distinguishes this destructive tool from sibling tools like 'add_option_to_custom_field', 'update_option_of_custom_field', and 'get_option_of_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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., the custom field must exist), consequences, or when to prefer other tools. Given the rich set of sibling tools, this is a significant gap.

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/martijnpieters/eduframe-mcp'

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