Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitter_tweet

Retrieve detailed information and engagement metrics for a specific tweet by URL, with optional trimmed responses and cached results to reduce credits.

Instructions

twitter: Tweet Details. GET /v1/twitter/tweet. Get detailed information about a specific tweet including engagement Costs 1 credit when it succeeds. 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": {
      "url": "<url>"
    },
    "name": "twitter_tweet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTweet URL
trimNoSet true for a trimmed response.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute real value on cost semantics: 1 credit on success, free on errors/blocked/timeout/invalid/cache hits, and conditional charging on not-found or empty results. However, it says nothing about authentication requirements, rate limits, or what the 'detailed information' payload actually contains, and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening purpose sentence is front-loaded, but the text is malformed ('including engagement Costs 1 credit') and three sentences are spent on billing detail while the actual purpose sentence is left incomplete. The raw endpoint path adds little for an agent.

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?

The description is adequate for a simple 3-parameter read tool with full schema coverage. The pricing behavior is unusually well documented, though the response contents remain underspecified and there is no output schema to compensate.

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%, so url, trim, and cache_max_age are already fully documented in the schema. The description adds no additional meaning about these parameters, so the baseline of 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?

States a specific verb and resource: 'Get detailed information about a specific tweet', with the endpoint GET /v1/twitter/tweet. It does not explicitly differentiate from siblings like twitter_user_tweets, and the phrase 'including engagement' is cut off by the pricing sentence, leaving the returned fields only vaguely characterized.

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?

The description never says when to use this tool versus alternatives such as twitter_user_tweets or twitter_profile, nor does it state prerequisites. Only billing context is given; the agent must infer that a single-tweet lookup is warranted when it already has a tweet URL.

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