Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get multiple Twitter profiles

twitter_profiles_batch_get
Read-onlyIdempotent

Fetch up to 50 X (Twitter) profiles in one request by handle or numeric user ID, returning a list for batch profile lookups.

Instructions

Get up to 50 X profiles in one request by handles and/or numeric user ids. Optional inputs: handle and id. Returns a list.

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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitter_profiles_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric X (Twitter) user id. Repeat this parameter for multiple ids.
handleNoX (Twitter) profile handle without the leading @. Repeat this parameter for multiple handles.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the 50-item ceiling and the return shape ('Returns a list'), but says nothing about what happens when a handle or id does not resolve, whether the result is ordered or padded with nulls, or any rate limits — all material for a batch lookup.

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

Conciseness4/5

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

Three short sentences with the batch scope and lookup keys front-loaded, so it is easy to scan. 'Returns a list.' is thin but not padded; nothing is redundant filler.

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

Completeness3/5

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

With no output schema, the description's only statement about results is 'Returns a list', which does not tell the agent what a list element contains or how misses are represented. The optional-vs-required error on `id` further reduces how safely an agent can call it, though the annotations compensate for the safety dimension.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description actively misleads: it calls `id` an 'Optional input' while the schema marks `id` as required. An agent trusting the prose could attempt a handle-only call that fails validation. The description also never mentions the injected `context`, `llm_model`, or `conversation_id` parameters, though the schema documents them well.

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?

States a specific verb and resource ('Get ... X profiles') plus the batch scope ('up to 50 ... in one request') and the lookup keys ('handles and/or numeric user ids'). It does not explicitly contrast itself with the single-profile sibling twitter_profile_get, so an agent must infer the batch-vs-single split from the name alone.

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 'and/or' phrasing usefully tells the agent that handle and id may be mixed in one call, which is real usage guidance. However there is no explicit when-to-use versus twitter_profile_get (single profile) or the mastodon/instagram batch siblings, and no prerequisites or failure conditions are stated.

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

Deploy Server

Other Tools