Nexscope Ecommerce Data MCP

Twitter Community Tweets

social_twitter_community_tweets

Read-only

Fetches tweets posted within a Twitter/X Community by URL. Returns an array of tweets, each with id, full_text, view_count, favorite_count, retweet_count, reply_count, bookmark_count, quote_count, created_at, and source. Each tweet includes a user object with the author's name, screen_name, avatar, followers_count, and is_blue_verified status. Completed lookups cost at least 10 Nexscope credits. Actual cost depends on the operation and requested options. Repeated requests may purchase data again. Twitter Community Tweets API View Pricing Get tweets from an X/Twitter Community. 1 credit per request Actual supplier units are reported per request. Examples are not guaranteed prices.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Community URL

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description goes beyond the readOnly/openWorld annotations by disclosing cost behavior ('Completed lookups cost at least 10 Nexscope credits', 'Repeated requests may purchase data again'), which is genuinely valuable for a paid lookup. However, the pricing text is internally inconsistent — it states 'at least 10 Nexscope credits' and then '1 credit per request' — and the trailing supplier boilerplate muddies rather than clarifies the cost model.

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?

The useful content (what it fetches, returned fields, cost) is front-loaded, but the tail is raw supplier boilerplate ('Twitter Community Tweets API View Pricing Get tweets from an X/Twitter Community. 1 credit per request... Examples are not guaranteed prices') that repeats the title and contradicts the earlier cost figure. The long field enumeration also adds bulk without helping invocation.

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?

With no output schema, enumerating the returned tweet and user fields is legitimately useful, and cost is disclosed. What is missing is volume/scope behavior: whether all community tweets are returned, any result cap, or pagination — relevant for a single-URL fetch that bills per request.

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% for the single `url` parameter ('Community URL'), so the schema already carries the burden. The description only reinforces that the URL refers to a Community rather than a tweet or profile, adding slight disambiguation but no format or syntax detail.

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 opens with a specific verb and resource ('Fetches tweets posted within a Twitter/X Community by URL'), which clearly separates it from social_twitter_community (community metadata) and social_twitter_user_tweets. It stops short of naming those siblings explicitly, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'posted within a Twitter/X Community by URL'; there is no explicit when-to-use, when-not-to-use, or named alternative such as social_twitter_user_tweets or social_twitter_search_posts. The tool's applicability is inferable but not stated.

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

All Nexscope Ecommerce Data MCP tools Inspect

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

Need Help?