AIsa X / Twitter

Batch Get User Info By UserIds

get_twitter_user_batch_info_by_ids

Read-onlyIdempotent

Usage-based billing; Default request estimate: $0.00018 USD (not a fixed price). Account-specific pricing and final settlement may differ.

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": {
      "userIds": "<userIds>"
    },
    "name": "get_twitter_user_batch_info_by_ids"
  }
}

Input Schema

Name	Required	Description	Default
`userIds`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026
- removedInput schema / properties / userIds / description
```
Removed value: -"Comma-separated user IDs"
```
- addedInput schema / properties / userIds / x-aisa-delimiter
```
Added value: +","
```
- addedInput schema / properties / userIds / x-aisa-maxItems
```
Added value: +100000
```
- addedInput schema / properties / userIds / x-aisa-minItems
```
Added value: +1
```
First observedSep 15, 2026

TDQS

D1.3/5.0

Behavior2/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds only a usage-based pricing estimate, which is useful cost context but does not explain batch size behavior, return format, rate limits, or any other operational trait. It does not contradict the annotations, but it adds very little beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and structured as a comment block, so it is not bloated. However, it is almost entirely irrelevant to tool selection and invocation, with no front-loaded purpose statement. The resulting definition is under-specified rather than concise in any useful sense.

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

Completeness1/5

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

For a batch user-lookup tool with one undocumented parameter and an output schema, the description provides no operational, semantic, or usage information. Only a billing estimate is present, leaving the definition critically incomplete for correct tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single input parameter, userIds, has 0% description coverage in the schema, and the description does not mention it at all. It does not explain the comma-delimited format, the 100,000 ID maximum, the 1 ID minimum, or what kinds of user identifiers are accepted. With low schema coverage, the description was required to compensate and completely failed to do so.

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

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description contains only a pricing boilerplate block and never states what the tool does. The name and title imply batch retrieval of Twitter users, but the description itself provides no verb, resource, or scope. This is a missing purpose, not merely a vague or tautological one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool, when not to, or how it relates to alternatives. In particular, it never mentions the single-user sibling get_twitter_user_info or explains when batch lookup is preferable. An agent is left to infer usage entirely from the tool name.

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

All AIsa X / Twitter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?