Skip to main content
Glama
hichana

Goal Story MCP Server

by hichana

goalstory_destroy_scheduled_story

Delete a scheduled story generation configuration by providing its unique identifier. This tool removes automated narrative setups from the goal management system.

Instructions

Delete a scheduled story generation configuration. Use with confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier of the scheduled story configuration to delete.

Implementation Reference

  • MCP tool registration and handler implementation. The async callback function executes the tool logic by making a DELETE HTTP request to the GoalStory API endpoint `/schedules/stories/{id}` using the doRequest helper, and formats the response as MCP tool output.
    DESTROY_SCHEDULED_STORY_TOOL.description, DESTROY_SCHEDULED_STORY_TOOL.inputSchema.shape, async (args) => { const url = `${GOALSTORY_API_BASE_URL}/schedules/stories/${args.id}`; const result = await doRequest(url, "DELETE"); return { content: [ { type: "text", text: `Scheduled story deleted:\n${JSON.stringify(result, null, 2)}`, }, ], isError: false, }; }, ); // -----------------------------------------
  • Tool definition including name, description, and Zod input schema for validating the 'id' parameter.
    export const DESTROY_SCHEDULED_STORY_TOOL = { name: "goalstory_destroy_scheduled_story", description: "Delete a scheduled story generation configuration. Use with confirmation.", inputSchema: z.object({ id: z .string() .describe( "Unique identifier of the scheduled story configuration to delete.", ), }), };
  • src/index.ts:25-25 (registration)
    Import of the tool definition from tools.ts for use in MCP server registration.
    DESTROY_SCHEDULED_STORY_TOOL,
  • Generic HTTP request helper used by all tool handlers, including this one, to perform API calls with authentication, error handling, and logging.
    async function doRequest<T = any>( url: string, method: string, body?: unknown, ): Promise<T> { console.error("Making request to:", url); console.error("Method:", method); console.error("Body:", body ? JSON.stringify(body) : "none"); try { const response = await axios({ url, method, headers: { "Content-Type": "application/json", Authorization: `Bearer ${GOALSTORY_API_TOKEN}`, }, data: body, timeout: 10000, // 10 second timeout validateStatus: function (status) { return status >= 200 && status < 500; // Accept all status codes less than 500 }, }); console.error("Response received:", response.status); return response.data as T; } catch (err) { console.error("Request failed with error:", err); if (axios.isAxiosError(err)) { if (err.code === "ECONNABORTED") { throw new Error( `Request timed out after 10 seconds. URL: ${url}, Method: ${method}`, ); } if (err.response) { // The request was made and the server responded with a status code // that falls out of the range of 2xx throw new Error( `HTTP Error ${ err.response.status }. URL: ${url}, Method: ${method}, Body: ${JSON.stringify( body, )}. Error text: ${JSON.stringify(err.response.data)}`, ); } else if (err.request) { // The request was made but no response was received throw new Error( `No response received from server. URL: ${url}, Method: ${method}`, ); } else { // Something happened in setting up the request that triggered an Error throw new Error(`Request setup failed: ${err.message}`); } } else { // Something else happened throw new Error( `Unexpected error: ${err instanceof Error ? err.message : String(err)}`, ); } } }

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/hichana/goalstory-mcp'

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