Skip to main content
Glama
Sign In
twikit-mcp

twikit-mcp

by tangivis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_scheduled_tweet

Schedule tweets for future posting by specifying a Unix timestamp and optional text or media. Plan your content in advance.

Instructions

Schedule a tweet to be posted at a future Unix timestamp.

Scheduled tweets follow X's standard rate limits, no special caveats needed.

Args: scheduled_at: Unix epoch seconds when the tweet should be posted (must be in the future). text: Tweet text. At least one of text or media_ids must be provided. media_ids: List of media IDs to attach to the scheduled tweet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scheduled_at": "<scheduled_at>"
    },
    "name": "create_scheduled_tweet"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
media_idsNo
scheduled_atYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.39
    • changedInput schema / properties / media_ids / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observedv0.1.33

TDQS

A4.3/5.0
Behavior3/5

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

The description discloses rate-limit behavior ('follow X's standard rate limits') and notes 'no special caveats needed,' which is useful. However, with no annotations, it carries the full burden and does not address potential side effects, permission requirements, or error behavior beyond the input constraints.

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 tightly written: a clear purpose sentence, a useful rate-limit note, and a well-organized Args list. Every sentence earns its place, and there is no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with an output schema, the description covers the essential purpose, all parameter semantics, and a key behavioral trait. Minor gaps like error conditions and lifecycle management (retrieval/deletion) are not explicitly mentioned, but the output schema and sibling tools help fill those gaps, so it is nearly complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by explaining all three parameters. It defines scheduled_at as Unix epoch seconds and requires future values, clarifies the dependency that at least one of text or media_ids must be provided, and describes media_ids as a list of attachment IDs.

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 opens with a specific verb ('Schedule') and resource ('a tweet') with a clear temporal scope ('future Unix timestamp'). This distinguishes it from immediate-posting siblings like send_tweet, and the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The first sentence provides clear context for when to use this tool: to schedule a tweet for a future time. It doesn't explicitly name alternatives or exclusions, but the 'future' constraint inherently signals that this is not for immediate posting, giving clear context without needing to mention send_tweet.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools