get_base_apitools_quotesV2Quotes by V2 Group: Tweets. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | ||
| tweetId | No | ||
| proxyUrl | No | ||
| resFormat | No | ||
| auth_token | No | web twitter login cookie info 'auth_token' |
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?
No behavioral information is disclosed beyond the tool name. The description does not mention side effects, return values, authentication needs, or rate limits. With no annotations provided, the description completely fails to compensate.
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 extremely short, which is concise, but this is under-specification rather than effective brevity. It lacks any structural elements like headings or a summary that would help an agent parse critical information.
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?
Given the tool's moderate complexity (5 params, no output schema, no annotations) and a large set of siblings, the description is utterly inadequate. It provides almost no contextual information for correct invocation.
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 only 20%, with only 'auth_token' documented in the schema. The description adds no insight into parameters like 'cursor', 'tweetId', 'proxyUrl', or 'resFormat'. This is a significant gap for a 5-parameter tool.
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 'Quotes by V2 Group: Tweets' is vague and does not clearly state the tool's function. It fails to specify that it retrieves or lists quotes, and does not distinguish it from the many sibling tools. The billing note adds no purpose clarity.
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 on when to use this tool versus alternatives. The description only mentions billing per call, which is not usage guidance. There is no mention of intended use cases, prerequisites, or exclusions.
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.