Skip to main content
Glama
Sign In
twikit-mcp

twikit-mcp

by tangivis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

send_tweet

Send a tweet to your Twitter account, with optional reply to an existing tweet by ID.

Instructions

Send a tweet. Optionally reply to a tweet by ID.

Args: text: Tweet content (max 280 chars). reply_to: Optional tweet ID to reply to.

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": {
      "text": "<text>"
    },
    "name": "send_tweet"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
reply_toNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.33

TDQS

A3.5/5.0
Behavior2/5

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

The description reveals the tool performs a write operation and mentions character limit, but lacks details on success behavior, error responses, idempotency, or potential side effects. Since no annotations exist, the description fails to provide sufficient behavioral transparency.

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 extremely concise with only two sentences and a brief argument list. Every word is necessary and front-loaded, making it efficient for an AI agent to parse quickly.

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 tool's simplicity and presence of an output schema, the description covers the basic purpose and parameters. However, it lacks usage context among siblings and does not address potential failures, making it incomplete for an agent to fully understand the tool's behavior.

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?

With 0% schema description coverage, the description adds meaningful value by specifying text max length (280 chars) and explaining reply_to as an optional tweet ID. This goes beyond the schema's simple type definitions, though the format of reply_to could be more precise.

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 it sends a tweet, optionally as a reply, which is a specific verb+resource combination. It distinguishes itself from other tweet-related tools like delete_tweet, retweet, and create_scheduled_tweet by focusing on sending a new tweet immediately.

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 like create_scheduled_tweet or send_dm. There is no mention of prerequisites, authentication, or rate limits, leaving the agent without context for appropriate usage.

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