Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

twitter_profile

Fetch Twitter profile statistics and metadata by handle; use optional cache age to lower credit costs.

Instructions

twitter: Profile. GET /v1/twitter/profile. Get Twitter profile information including stats and metadata 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": {
      "handle": "<handle>"
    },
    "name": "twitter_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesTwitter handle
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.1/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 disclose a fairly detailed billing model: 1 credit on success, zero cost for errors, blocked/timed-out requests, invalid requests and cache hits. However, it says nothing about authentication requirements, rate limits, or what the returned profile object contains beyond a vague 'stats and metadata', leaving meaningful behavioral gaps.

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 purpose is front-loaded in the first two sentences, which is good. But the route path repeats the tool identity, and the trailing cost paragraph is long and hedged ('charged only where that operation's published cost says so'), spending words without adding actionable clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should characterize return values more than 'stats and metadata', and it omits auth prerequisites entirely. The cost behavior is well covered, but for a profile-fetch tool with no annotations the definition is only adequate.

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 coverage is 100%, so both parameters (handle, cache_max_age) are already documented, and the baseline is 3. The description's note that cache hits cost nothing reinforces the cache_max_age parameter's purpose slightly, but it adds no syntax, format, or constraint detail beyond the schema.

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 states a specific verb and resource ('Get Twitter profile information including stats and metadata') and names the underlying route GET /v1/twitter/profile, so an agent knows exactly what it retrieves. The platform qualifier 'twitter' distinguishes it from the many sibling *_profile tools, though the description does not explicitly say so.

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?

There is no guidance on when to choose this over alternatives such as twitter_user_tweets or the other platform profile tools, and no prerequisites or exclusions are stated. The only usage-adjacent information is the cost model, which is not a selection criterion.

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