Skip to main content
Glama
Sign In

Superpowers.social

by social.superpowers
OverviewDiscussionsAdmin

Search Twitter

twitter-search
Read-onlyIdempotent

Search X/Twitter for tweets matching a query. Returns token-optimized results with engagement metrics.

Input Schema

NameRequiredDescriptionDefault
countNoNumber of results to return (default 10, max 100). Up to 20 results costs 1 call credit; each further 20 costs one more. For long pulls prefer count 20 plus cursor.
queryYesSearch query string
cursorNoPagination cursor from a previous response
text_onlyNoReturn only {id, text} per tweet; quoted tweets keep their text. Drops author, date, URL, and reply/retweet/like counts. Use when you only need tweet contents, e.g. summarising or scanning many results. Leave false when you need to cite authors, link to tweets, filter by date, or rank by engagement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / count / description
      Previous value: -"Number of results to return (default 10)"New value: +"Number of results to return (default 10, max 100). Up to 20 results costs 1 call credit; each further 20 costs one more. For long pulls prefer count 20 plus cursor."
  2. Changed1 schema field changed
    • changedInput schema / properties / text_only / description
      Previous value: -"If true, return only id and text per tweet to save tokens."New value: +"Return only {id, text} per tweet; quoted tweets keep their text. Drops author, date, URL, and reply/retweet/like counts. Use when you only need tweet contents, e.g. summarising or scanning many results. Leave false when you need to cite authors, link to tweets, filter by date, or rank by engagement."
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'token-optimized' and include 'engagement metrics,' which is useful return-shape context. However, it does not describe rate limits, auth needs, pagination behavior, or what happens with long pulls beyond what the schema already says.

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?

The description is two short sentences with no wasted language. The purpose is front-loaded and immediately identifies the operation and return characteristics. It is appropriately sized for a schema that already carries detailed parameter documentation.

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?

The tool is relatively simple and the schema thoroughly covers parameters, while annotations cover the safety profile. However, with no output schema, the description only minimally explains return values as 'token-optimized results with engagement metrics' and does not address sibling selection. It is adequate but has clear gaps.

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 all four parameters are already well documented in the schema, including count credits, cursor pagination, and text_only tradeoffs. The description adds no parameter-specific detail beyond naming the query concept. Baseline 3 is appropriate when the schema carries parameter semantics.

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: 'Search X/Twitter for tweets matching a query.' This clearly identifies the tool as the tweet-search operation. It does not explicitly distinguish itself from siblings such as twitter-read, twitter-thread, twitter-user-tweets, or twitter-news, so it falls short of the top score.

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 gives no guidance on when to use this tool versus alternatives. It does not mention siblings like twitter-read, twitter-thread, twitter-user-tweets, or twitter-news, nor does it state exclusions or selection criteria. The purpose implies searching, but usage is not actively guided.

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

All Superpowers.social 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