Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

x_twitter_public_search_tweets_scraper

Read-onlyIdempotent

X (Twitter) Public Tweets & Profile Scraper (No Cookies): Real-time structured data extraction feed for X (Twitter) Public Tweets & Profile Scraper (No Cookies).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x_twitter_public_search_tweets_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. Added

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one genuinely new behavioral fact — "No Cookies," i.e. no auth/session credentials needed — and claims "real-time" freshness, but says nothing about rate limits, pagination, or what a record contains.

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

Conciseness2/5

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

It is short, but the length comes from circular restatement: the tool name is repeated twice inside a single sentence that conveys no additional information. Nothing is front-loaded because there is no substantive content to prioritize.

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

Completeness2/5

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

This is a search/scrape tool with no output schema and no description of the returned record structure, result scope, or pagination behavior. Combined with the absence of any query parameter, an agent cannot determine from the definition what it will actually receive or how to target the search.

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?

With a single parameter at 100% schema description coverage, the schema already explains maxResults, so the baseline of 3 applies. The description adds no meaning beyond it — notably it never explains what is being searched given that no query term parameter exists, leaving maxResults' effect on results unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name and title nearly verbatim ("Real-time structured data extraction feed for X (Twitter) Public Tweets & Profile Scraper (No Cookies)"), which is tautology rather than a statement of what the tool does. An agent can infer the resource (X public tweets and profiles) from the name, but the description adds no verb, scope, or differentiation from siblings like reddit_subreddit_search_posts_scraper.

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 when-to-use guidance, no exclusions, and no mention of alternatives. The only usage-relevant hint is the parenthetical "No Cookies," which implies no authentication is required, but nothing tells an agent under what circumstances to pick this tool over the other social/community scrapers.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources