ScrapeCreators MCP Server

Community

twitter_community

Fetch detailed Twitter/X Community info by URL, including name, description, member count, rules, creator profile, and recent member avatars. Requires confirm=true for paid API calls.

Instructions

Retrieves details about a Twitter/X Community by URL. Returns the community name, description, rest_id, join_policy, created_at, member_count, rules, and creator_results with the creator's profile. Also includes members_facepile_results with avatar images of recent members. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

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

Input Schema

Name	Required	Description
`url`	Yes	Community URL
`account`	No	Named private ScrapeCreators account; selects credentials, not a remote account ID.
`confirm`	No	Must be true for the specific approved credit-consuming research call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Without the description, readOnlyHint=false would misleadingly suggest a mutating tool; the description resolves this by explaining that read-like POSTs do not publish to social platforms, which is exactly the context annotations cannot convey. It also discloses paid-credit consumption and the confirm gate, though it says nothing about idempotency or rate limits.

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?

Two tight paragraphs, front-loaded with the action and followed by the cost/confirm caveat; the return-field enumeration is dense but useful. Slight redundancy between the description's confirm note and the schema's, but nothing wasted.

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

Completeness4/5

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

With no output schema, the description takes on the burden of describing the return payload and does so explicitly (name, rest_id, join_policy, member_count, rules, creator_results, members_facepile_results). Combined with the credit and confirm disclosure, an agent has what it needs, though channel/error behavior is unstated.

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 url, account, and confirm are already documented; the description reinforces confirm's credit gate ('requires confirm=true') but adds no format or syntax detail for the url parameter. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose5/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 ('Retrieves details about a Twitter/X Community by URL') and enumerates the returned fields, so an agent can distinguish it from twitter_profile, twitter_user_tweets, and twitter_community_tweets without opening any schema.

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?

It gives the operating precondition ('requires confirm=true') and a cost warning ('potentially consumes paid API credits'), which is real usage guidance. However, it never names the obvious alternative (twitter_community_tweets) or states when to pick this tool over another Twitter tool, so routing is left implicit.

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

Deploy Server