Skip to main content
Glama
Sign In

TwittrAPI

by io.github.twittrapi
OverviewDiscussionsAdmin

Get "About this account" for many users

get_user_about_batch
Read-onlyIdempotent

Get the "About this account" data (country the account is based in, username changes, verification) of up to 20 accounts in one call. Returns raw JSON: one entry per handle, in order, plus errors for handles that could not be looked up.

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": {
      "usernames": "<usernames>"
    },
    "name": "get_user_about_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_charsNoMaximum characters of JSON to return (default 50000). Longer output is cut with a [TRUNCATED] marker. Lower it to save context, raise it if you need the full response.
usernamesYesAccounts to look up, 1 to 20 X handles (a leading @ is fine). Billed as one call per handle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so safety is covered. The description goes beyond them by disclosing the return shape: raw JSON, one entry per handle in input order, plus per-handle errors for failed lookups. It omits cost implications ('billed as one call per handle'), which live only in the schema.

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

Conciseness5/5

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

Two sentences with no filler: the capability and batch limit come first, the return contract second. Every clause carries information an agent needs before calling.

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

Completeness4/5

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

There is no output schema, so the description must carry return-value disclosure, and it does so adequately by specifying raw JSON, ordering, and per-handle error entries. It could still say what an error entry looks like or whether partial results are returned when some handles fail, but the essentials are present for a two-parameter read tool.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (usernames, max_chars) are already fully documented, including the @-prefix tolerance, the 1-20 range, truncation behavior and per-handle billing. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource ('Get the "About this account" data') and adds scope ('up to 20 accounts in one call'), which lets an agent distinguish this batch lookup from single-user siblings like get_user_by_username. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

The phrase 'in one call' implies this is the efficient path when looking up several handles, but there is no explicit when-to-use or when-not guidance and no pointer to the single-handle alternative. The agent must infer the choice from the batch limit alone.

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

All TwittrAPI toolsInspect
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