Skip to main content
Glama
Sign In
Spectre

Spectre

by pranrichh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

post_tweet

Post tweets on X/Twitter with support for replies, quotes, and media uploads.

Instructions

Post a new tweet on X/Twitter.

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": "post_tweet"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesTweet content (max 280 chars for standard, 25k for Premium).
reply_toNoOptional tweet ID to reply to.
media_idsNoComma-separated media IDs from upload_media (e.g. "123456,789012").
quote_tweetNoOptional tweet ID to quote.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as authentication requirements, rate limits, or potential failures (e.g., content policy violations). The description is too brief to add value beyond the tool's name.

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 a single sentence, very concise with no wasted words. It gets the main point across efficiently, though it could add a bit more context without becoming verbose.

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 (4 parameters, many siblings) and the presence of an output schema, the description is insufficient. It omits side effects, prerequisites, and interaction details (e.g., media upload dependency), leaving gaps for an AI agent.

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?

Input schema has 100% description coverage, so parameters are well-documented. The description adds no extra meaning beyond the schema, which already includes character limits and usage notes for reply_to, media_ids, and quote_tweet.

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

Purpose4/5

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

The description clearly states 'Post a new tweet on X/Twitter,' specifying the action (post) and resource (tweet). It is straightforward but does not differentiate from similar siblings like schedule_tweet or create_draft.

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 on when to use this tool versus alternatives (e.g., schedule_tweet for delayed posting, create_draft for unsent drafts). The description lacks 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