Skip to main content
Glama

delete_custom_record

DestructiveIdempotent

Delete a custom record by specifying the parent resource ID and the record ID.

Instructions

Delete a custom record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_slugYesID of the parent resource
idYesID of the custom record to delete

Implementation Reference

  • The handler function for the delete_custom_record tool. It calls apiDelete with the path /custom/objects/{object_slug}/records/{record_id}, logs the response, and formats the result using formatDelete. Note: Line 91 has a bug - it uses 'record_id' instead of 'id'.
    async ({ object_slug, id }) => {
      try {
        const record = await apiDelete<EduframeRecord>(`/custom/objects/${object_slug}/records/${record_id}`);
        void logResponse("delete_custom_record", { object_slug, id }, record);
        return formatDelete(record, "custom record");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for delete_custom_record: requires object_slug (positive int, ID of parent resource) and id (positive int, ID of custom record to delete).
    inputSchema: {
      object_slug: z.number().int().positive().describe("ID of the parent resource"),
      id: z.number().int().positive().describe("ID of the custom record to delete"),
    },
  • Registration of delete_custom_record tool on the MCP server via registerTool() with description and annotations (destructiveHint: true).
    server.registerTool(
      "delete_custom_record",
      {
        description: "Delete a custom record",
        annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
        inputSchema: {
          object_slug: z.number().int().positive().describe("ID of the parent resource"),
          id: z.number().int().positive().describe("ID of the custom record to delete"),
        },
      },
      async ({ object_slug, id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(`/custom/objects/${object_slug}/records/${record_id}`);
          void logResponse("delete_custom_record", { object_slug, id }, record);
          return formatDelete(record, "custom record");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Import of registerCustomRecordTools from custom_records.ts, which registers delete_custom_record along with other custom record tools.
    import { registerCustomRecordTools } from "./custom_records";
    import { registerDiscountCodeTools } from "./discount_codes";
    import { registerEditionDescriptionSectionTools } from "./edition_description_sections";
    import { registerEducatorTools } from "./educators";
    import { registerEmailTools } from "./emails";
    import { registerEnrollmentTools } from "./enrollments";
    import { registerGradeTools } from "./grades";
    import { registerInvoiceVatTools } from "./invoice_vats";
    import { registerInvoiceTools } from "./invoices";
    import { registerLabelTools } from "./labels";
    import { registerLeadTools } from "./leads";
    import { registerMaterialGroupTools } from "./material_groups";
    import { registerMaterialTools } from "./materials";
    import { registerMeetingLocationTools } from "./meeting_locations";
    import { registerMeetingTools } from "./meetings";
    import { registerOrderTools } from "./orders";
    import { registerOrganizationTools } from "./organizations";
    import { registerPaymentMethodTools } from "./payment_methods";
    import { registerPaymentOptionTools } from "./payment_options";
    import { registerPaymentTools } from "./payments";
    import { registerPlannedCourseTools } from "./planned_courses";
    import { registerPlanningAttendeeTools } from "./planning_attendees";
    import { registerPlanningConflictTools } from "./planning_conflicts";
    import { registerPlanningEventTools } from "./planning_events";
    import { registerPlanningLocationTools } from "./planning_locations";
    import { registerPlanningMaterialTools } from "./planning_materials";
    import { registerPlanningRequiredTeacherGroupAttendeeTools } from "./planning_required_teacher_group_attendees";
    import { registerPlanningTeacherTools } from "./planning_teachers";
    import { registerProgramEditionTools } from "./program_editions";
    import { registerProgramElementTools } from "./program_elements";
    import { registerProgramEnrollmentTools } from "./program_enrollments";
    import { registerProgramPersonalProgramElementTools } from "./program_personal_program_elements";
    import { registerProgramProgramTools } from "./program_programs";
    import { registerReferralTools } from "./referrals";
    import { registerSignupQuestionTools } from "./signup_questions";
    import { registerTaskTools } from "./tasks";
    import { registerTeacherEnrollmentTools } from "./teacher_enrollments";
    import { registerTeacherRoleTools } from "./teacher_roles";
    import { registerTeacherTools } from "./teachers";
    import { registerTheseTools } from "./theses";
    import { registerUserTools } from "./users";
    import { registerWebhookNotificationTools } from "./webhook_notifications";
    import { registerWebhookTools } from "./webhooks";
    
    const tools: Array<(server: McpServer) => void> = [
      registerAccountTools,
      registerAffiliationTools,
      registerAttendanceTools,
      registerAuthenticationTools,
      registerCatalogProductTools,
      registerCatalogVariantTools,
      registerCategorieTools,
      registerCertificateTools,
      registerCommentTools,
      registerCourseLocationTools,
      registerCourseTabTools,
      registerCourseVariantTools,
      registerCourseTools,
      registerCreditCategorieTools,
      registerCreditTools,
      registerCustomAssociationTools,
      registerCustomFieldOptionTools,
      registerCustomObjectTools,
      registerCustomRecordTools,
  • The apiDelete function used by the handler to perform DELETE HTTP requests to the Eduframe API.
    export async function apiDelete<T>(path: string): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path);
    
      const response = await fetch(url.toString(), {
        method: "DELETE",
        headers: buildHeaders(token),
      });
    
      return handleResponse<T>(response);
    }
Behavior3/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description confirms deletion but adds no extra context about side effects, permissions, or behavior. It does not contradict 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 extremely concise (3 words) and front-loaded. It efficiently conveys the core action without waste, though it could be expanded slightly for completeness.

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?

Given the simple operation and presence of annotations, the description is minimally adequate. It does not mention return behavior or error cases, but the input schema and annotations cover essential aspects.

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 descriptions cover both parameters (object_slug and id) with meaningful descriptions. The tool description adds no further semantic value, so it meets the baseline for high coverage.

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 'Delete a custom record', using a specific verb and resource. It distinguishes itself from sibling tools like create_custom_record and update_custom_record, leaving no ambiguity.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, constraints, or scenarios where this tool is appropriate, leaving the agent without context.

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