ShipPost MCP

reply_to_tweet

Post a public reply to a specific tweet using the authenticated account's ID and text.

Instructions

Reply to a specific tweet.

Posts a public reply to the given tweet from the authenticated user's account.

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

Input Schema

Name	Required	Description	Default
`text`	Yes	The reply text (max 280 characters)
`tweet_id`	Yes	The ID of the tweet to reply to

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully discloses that the reply is public and posted from the authenticated user's account, but it does not mention potential failure modes, rate limits, irreversibility, or other side effects. Basic context is present, but richer behavioral transparency is missing.

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 two short sentences with no filler. The first sentence is a clear one-line summary, and the second adds the important public/authenticated context. Every word earns its place.

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 low-complexity tool with only two parameters and an output schema, the description is mostly complete: it states the action, the public nature, and the authenticated account context. It lacks explicit usage exclusions, but the simplicity and schema coverage compensate, leaving only minor gaps.

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 input schema has 100% description coverage for both parameters (tweet_id and text), so the schema already carries the parameter meaning. The description adds little beyond 'given tweet' and 'reply text,' which does not meaningfully exceed the schema's existing explanations.

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 action ('Reply to a specific tweet') and resource ('the given tweet'), and adds that it posts a public reply from the authenticated user's account. This distinguishes it from siblings like post_tweet or draft_reply by focusing on replying to an existing tweet.

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

Usage Guidelines3/5

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

The description implies when to use this tool—when replying to a specific tweet—but does not explicitly contrast it with alternatives like post_tweet (new tweet) or draft_reply (drafting without posting). There is no when-not-to-use guidance or named alternative tools.

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

Deploy Server