ShipPost MCP

search_tweets

Search recent tweets by keyword or phrase. Get tweet text, author, engagement metrics, and URLs from the last 7 days, excluding retweets.

Instructions

Search recent tweets by keyword or phrase.

Searches the last 7 days of public tweets. Retweets are excluded. Returns tweets with text, author, engagement metrics, and URLs.

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": {
      "query": "<query>"
    },
    "name": "search_tweets"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query (e.g. "AI startups", "from:username", "#buildinpublic")
`max_results`	No	Number of results to return (10-100, default 10)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden. It meaningfully discloses the 7-day lookback, retweet exclusion, and returned fields (text, author, engagement metrics, URLs). It does not mention pagination or rate limits, but the core behavior is transparent enough for selection.

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?

Three short sentences: the headline purpose comes first, followed by essential scope and result details. There is no filler or redundant phrasing.

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?

Given two simple parameters, a full output schema, and a clear sibling context, the description adequately covers the tool's scope and result content. It could note ordering or pagination, but those are not critical for correctly selecting and invoking this search tool.

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?

Schema description coverage is 100%, with query and max_results fully described including examples and default ranges. The tool description adds no parameter-specific detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb+resource ('Search recent tweets by keyword or phrase') and further narrows scope with the 7-day window and exclusion of retweets, making it clearly distinct from sibling tools like get_timeline, get_mentions, and get_tweet.

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?

It clearly states the search covers the last 7 days of public tweets and excludes retweets, giving useful context for when to use this tool. It does not explicitly name alternative tools for non-search cases, but the keyword-search purpose is unambiguous.

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

Deploy Server