get_base_apitools_setBannerImgset Banner Img Group: other. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| ct0 | No | ||
| apiKey | No | ||
| proxyUrl | No | ||
| bannerUrl | No | banner online url | |
| 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?
With no annotations provided, the description carries the full burden of disclosing behavioral traits. It fails entirely—no mention of side effects, authentication requirements, rate limits, or what the 'per call' credit means in practice. The billing note is unhelpful without context.
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 brief at 11 words, but this represents under-specification rather than effective conciseness. It fails to provide essential details, making it an inadequate substitute for substantive guidance.
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?
This is a mutation-like operation (setting a banner) with zero annotation coverage, no output schema, and 6 parameters mostly undocumented. The description is completely inadequate for an agent to understand the tool's behavior, requirements, or effects, especially given the large context of similar API tools.
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 coverage is only 17% with 5 of 6 parameters undocumented (ct0, apiKey, proxyUrl, resFormat, auth_token). The only parameter description, 'banner online url' for bannerUrl, adds minimal value. The description text contributes nothing beyond the schema.
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 'set Banner Img' uses a specific verb and object, indicating the tool configures a banner image URL. However, it largely restates the tool name and does not differentiate from similar siblings like setHeadImg or setHeadImgByFile, leaving ambiguity about what makes this tool distinct.
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 usage guidance is provided. The description contains only a title repeat and billing note, with no mention of when to use this tool versus alternatives such as setHeadImg or setHeadImgByFile, and no 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.