Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitter_user_tweets

Fetch up to 100 popular public tweets from a Twitter user's profile by handle to analyze notable posts instead of only recent updates.

Instructions

twitter: User Tweets. GET /v1/twitter/user-tweets. Get up to 100 popular tweets from a user's public profile, not their latest tweets. Costs 1 credit when it succeeds. Costs 0 credits when tweets is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "handle": "<handle>"
    },
    "name": "twitter_user_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet true for a trimmed response.
handleYesTwitter handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the result ordering (popularity-ranked, not chronological), the 100-item ceiling, and a detailed credit model including the zero-cost paths (empty tweets, errors, blocked/timeouts, invalid requests, cache hits). It does not address pagination, result freshness, or any auth/rate-limit constraints, which leaves some operational gaps for a read tool.

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?

Front-loaded with the resource and the key behavioral distinction (popular vs. latest) before the pricing detail. Every sentence carries information; even the pricing sentence is dense with distinct cost rules rather than 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 two-parameter read tool with no annotations and no output schema, the description supplies the essentials an agent needs: what is returned, how it is ranked, how many, and what it costs. The remaining gap is return-shape/pagination detail, which is mildly consequential given no output schema exists to cover it.

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% and both parameters are documented in the schema, including a handle example ("NASA"). The description adds nothing about handle format or what `trim` changes in the response, so the baseline 3 applies.

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?

Names a specific verb and resource ("Get ... tweets from a user's public profile"), states the cap (up to 100) and a key qualifier ("popular tweets ... not their latest tweets"). That negation preempts the most likely misconception, but no sibling tool (e.g. twitter_profile, bluesky_user_posts) is named to sharpen the boundary.

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?

Usage is implied by 'popular tweets from a user's public profile, not their latest tweets', which tells the agent what kind of result it gets. There is no explicit when-to-use vs. alternative (e.g. profile endpoint or a latest-timeline tool), and no prerequisite or exclusion guidance beyond the 'popular' caveat.

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