post_base_apitools_unlockTwitter account unlock(Additional purchases required) Group: other. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| ct0 | No | ||
| No | |||
| apiKey | No | ||
| proxyUrl | No | ||
| emailCode | No | ||
| emailPass | No | ||
| resFormat | No | ||
| auth_token | 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?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state what account unlocking entails, whether it modifies account state, what credentials are needed, what errors or side effects occur, or what the response looks like. The billing note only adds pricing context, not behavioral transparency.
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, but this is under-specification rather than concise effectiveness. 'Twitter account unlock' repeats the title, while 'Group: other' and billing information add little operational value and do not earn their place.
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?
With eight undocumented parameters, no annotations, and no output schema, the description is far too incomplete to support correct invocation. It does not explain required inputs, authentication flow, result format, or any usage context, making it inadequate for an agent to select and use the tool.
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 provides no meaning for any of the eight parameters (ct0, email, apiKey, proxyUrl, emailCode, emailPass, resFormat, auth_token). The description fails to compensate for the schema's complete lack of parameter documentation.
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 essentially a restatement of the tool name/title: 'Twitter account unlock(Additional purchases required).' It lacks a specific verb phrase or operational explanation, making it a tautology rather than a clear purpose statement. The extra metadata ('Group: other. Billing per call: 1 Credits.') does not clarify what the tool actually does.
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?
There is no guidance on when to use this tool versus alternatives such as get_base_apitools_unlock or other account-related tools. 'Additional purchases required' hints at a prerequisite but does not explain the context, preconditions, or when this unlock should be invoked.
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.