get_base_apitools_CommunitiesSearchV2get Communities Member list. Group: communities. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| word | No | ||
| apiKey | No | ||
| cursor | No | ||
| proxyUrl | No | ||
| resFormat | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavior, but it only adds 'Group: communities' and 'Billing per call: 1 Credits.' It does not mention required authentication, pagination behavior, data scope, or whether this is a read-only search.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded, but the first sentence is redundant with the title and 'Group: communities' mostly repeats the tool name. It is concise in size but not in informative value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 5 undocumented parameters, no annotations, and no output schema, this description is severely incomplete. It does not describe return format, expected inputs, prerequisites, or behavior, so an agent cannot reliably select or invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description adds no meaning for the five parameters (word, apiKey, cursor, proxyUrl, resFormat). The agent is left without any indication which parameters matter or how they control the community member list.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is identical to the title ('get Communities Member list.') and merely restates the tool's name without explaining what the search or member-list operation actually does. It does not distinguish this from sibling tools like CommunitiesMemberV2 or CommunitiesTimelineV2.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool instead of the many sibling community/list tools. It only gives a group label and billing cost, so the agent cannot determine the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set is full of confusing variants such as get_/post_ prefixed duplicates of the same endpoints, competing V1/V2 versions of the same action (e.g., followersList vs. followersListV2), and poorly described tools like CommunitiesSearchV2 and getCt0 that give no clear unique purpose. Agents would frequently need to guess between similar tools for a single task.
Naming is chaotic, mixing camelCase (getDMS, likeV2), PascalCase (CreateNoteTweet, CommunitiesMemberV2), and inconsistent prefixes (gettools_*, get_*, post_*) with duplicated operations. The 'get_/post_' prefixes appear to indicate API method rather than action, but they are applied inconsistently, with some tools appearing under both and others only once. There is no predictable verb_noun pattern throughout.
With 107 tools, the server is extremely large, far exceeding the 50+ threshold for extreme mismatch, and this count is inflated by duplicates (many get_/post_ twins) and overlapping V1/V2 variants. Even the unique tool set is likely around 60-70, which is still an unwieldy surface for an agent to negotiate. This severely disrupts coherence.
The tool set covers most core Twitter/X domains: tweets, likes, retweets, follows, DMs, search, communities, lists, and profile management. However, it is cluttered with duplicates and lacks some obvious pieces like mute/unmute operations or a direct 'update tweet' action, and several tools appear to be thin wrapper variations of the same endpoint. Coverage is broad but not cleanly organized.