Skip to main content
Glama
Sign In

ScrapeIO

by com.scrapeio
OverviewDiscussionsAdmin

twitter_search_posts

Read-only

X's Top results for a keyword, with views and likes. (1 credit)

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": "twitter_search_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text.
cursorNoCursor from the previous page's data.cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new context: results are ranked as 'Top' rather than chronological, each result carries view and like counts, and the call costs 1 credit — a billing trait no structured field conveys.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the credit note is compactly parenthesized. Slightly cryptic phrasing ('X's Top results') costs it a point but nothing is wasted.

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?

For a two-parameter read tool with annotations and full schema coverage, the essentials are present, and it even discloses the credit cost and returned engagement fields. It still leaves unclear how many results come back, what 'Top' ranking means, and how to page with the cursor.

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 'query' and 'cursor' are already documented. The description hints that 'query' is a keyword driving a ranked search, but says nothing about the cursor or pagination flow, so it does not exceed the schema baseline.

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 resource and scope: 'Top results for a keyword' on X, with the engagement fields returned. An agent can tell this is a keyword search of posts, though the distinction from the sibling twitter_search is not spelled out.

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?

No when-to-use guidance, no exclusions, and no mention of the sibling tools (twitter_search, twitter_user_tweets, twitter_trends) that an agent would need to choose between. The only implied guidance is 'keyword' versus the profile/user-scoped siblings.

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

All ScrapeIO toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources