Skip to main content
Glama

timeline_remove_scheduled_event

Delete a scheduled social media post by providing its event ID to manage content automation workflows across multiple platforms.

Instructions

Remove a scheduled event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYes

Implementation Reference

  • The complete tool registration including the handler function that deletes the specified scheduled event from the database using its eventId. It uses the getDb() helper and the events table schema.
    mcp.addTool({
      name: 'timeline_remove_scheduled_event',
      description: 'Remove a scheduled event',
      parameters: z.object({
        eventId: z.string().uuid()
      }),
      execute: async (params) => {
        const db = await getDb();
        
        await db.delete(events).where(eq(events.id, params.eventId));
        
        return JSON.stringify({
          success: true,
          message: `Event ${params.eventId} removed successfully`
        }, null, 2);
      }
    });
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 of behavioral disclosure. 'Remove' implies a destructive mutation, but the description doesn't specify whether this action is reversible, requires specific permissions, affects related data, or has side effects (e.g., notifications). It lacks details on error handling, rate limits, or response format, leaving significant gaps in understanding the tool's behavior.

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 with a single sentence ('Remove a scheduled event'), which is front-loaded and wastes no words. While it could benefit from more detail, it efficiently communicates the core action without redundancy or fluff, earning a high score for brevity and clarity in structure.

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 complexity (a destructive mutation with no annotations, 0% schema coverage, and no output schema), the description is incomplete. It doesn't explain what happens upon removal, potential errors, or return values, leaving critical aspects undocumented. For a tool that modifies data, this lack of context makes it inadequate for safe and effective use.

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?

The description adds no parameter semantics beyond what the input schema provides. With 0% schema description coverage, the single parameter 'eventId' is undocumented in both the schema and description. However, since there's only one parameter and its purpose (identifying the event to remove) is somewhat inferable from context, this meets the baseline for minimal viability without compensating for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Remove') and resource ('a scheduled event'), which provides a basic understanding of what the tool does. However, it doesn't differentiate from sibling tools like 'timeline_remove_track' or specify what constitutes a 'scheduled event' versus other event types. The purpose is clear but lacks specificity about scope or distinction from alternatives.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing event ID), exclusions, or comparisons with siblings like 'timeline_update_scheduled_event' or 'timeline_list_scheduled_events'. Without such context, users must infer usage from the tool 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/derekalia/timeline-mcp'

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