Skip to main content
Glama
pascalporedda

Typefully MCP Server

get_scheduled_drafts

Fetch recently scheduled Twitter drafts from Typefully to review or reschedule your upcoming posts.

Instructions

Get recently scheduled drafts from Typefully.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'get_scheduled_drafts' in the CallToolRequestSchema switch statement. Calls client.getScheduledDrafts() and formats the response.
    case 'get_scheduled_drafts': {
      const drafts = await this.client.getScheduledDrafts();
      
      return {
        content: [
          {
            type: 'text',
            text: `Found ${drafts.length} scheduled drafts:\n\n${drafts
              .map((draft) => `ID: ${draft.id}\nContent: ${draft.content.substring(0, 100)}...\nScheduled: ${draft.scheduled_date}\n`)
              .join('\n')}`,
          },
        ],
      };
    }
  • The TypefullyClient method getScheduledDrafts() that makes the HTTP GET to '/drafts/recently-scheduled/' and validates the response with GetDraftsResponseSchema.
    async getScheduledDrafts(): Promise<Draft[]> {
      const response = await this.client.get('/drafts/recently-scheduled/');
      const validatedResponse = GetDraftsResponseSchema.parse(response.data);
      return validatedResponse.drafts;
    }
  • src/server.ts:71-77 (registration)
    Tool registration listing in ListToolsRequestSchema handler, defining the tool name, description, and empty inputSchema.
      name: 'get_scheduled_drafts',
      description: 'Get recently scheduled drafts from Typefully.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Zod schemas for DraftSchema and GetDraftsResponseSchema used to validate the scheduled drafts response.
    export const DraftSchema = z.object({
      id: z.string(),
      content: z.string(),
      scheduled_date: z.string().nullable(),
      created_at: z.string(),
      updated_at: z.string(),
      share_url: z.string().optional(),
      auto_retweet_enabled: z.boolean().optional(),
      auto_plug_enabled: z.boolean().optional(),
    });
    
    export const GetDraftsResponseSchema = z.object({
      drafts: z.array(DraftSchema),
    });
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It does not specify that this is a read-only operation, what 'recently' means (e.g., time window), or any edge cases like empty results.

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

Conciseness5/5

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

The description is a single sentence with no wasted words. It is front-loaded with the action and resource, achieving maximum conciseness.

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 lack of parameters or output schema, the description is minimally sufficient. However, it omits details like the time range or sort order for 'recently', leaving some ambiguity.

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

Parameters4/5

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

There are no parameters (zero params, baseline 4). The description adds the qualifier 'recently' which provides some semantic context beyond the empty schema, indicating a time-based filter.

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 the verb 'Get' and the resource 'scheduled drafts' with the source 'Typefully'. It distinguishes from siblings like 'create_draft' (creation) and 'get_published_drafts' (published vs scheduled).

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. No mention of when not to use it or any context-dependent conditions.

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/pascalporedda/typefully-mcp-server'

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