Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitter profile

twitter_profile_get
Read-onlyIdempotent

Fetch an X (Twitter) profile by handle or numeric user ID to retrieve follower and tweet metrics plus account age signals for identity and credibility checks.

Instructions

Get an X (Twitter) profile by handle or numeric user id. Requires handle. Returns lookupStatus plus follower/tweet metrics and account age signals.

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

Input Schema

NameRequiredDescriptionDefault
byNoTreat the path value as a handle or a numeric user id. Defaults to id when the value is all digits.
handleYesRequired. X (Twitter) profile handle without the leading @, or a numeric user id.
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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape ('lookupStatus plus follower/tweet metrics and account age signals'), which matters because there is no output schema. It omits auth needs and rate-limit behavior, keeping it below a 5.

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 tight sentences with no filler, front-loading the core action and then the return contract. Every clause carries information an agent can act on.

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?

With no output schema, the description usefully sketches the return payload (lookupStatus, follower/tweet metrics, account age), which is what an agent most needs here. It leaves the interaction between the 'by' enum and the 'handle' field implicit, and says nothing about failure modes for suspended or nonexistent accounts, so it is strong but not fully complete.

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 every parameter is already documented in the input schema. The description restates the handle requirement and the handle-or-numeric-id option but adds no syntax or formatting detail beyond what the schema says. The baseline of 3 for full schema coverage is appropriate.

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 gives a specific verb and resource: 'Get an X (Twitter) profile by handle or numeric user id.' That clearly separates it from sibling sub-resource tools like twitter_profile_followers_list or twitter_profile_tweets_list. It does not explicitly name or differentiate itself from other platform profile getters such as bluesky_profile_get, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description states a requirement ('Requires handle') but offers no guidance on when to choose this tool over its many profile-related siblings or on batch/profile-about alternatives. There are no when-not-to-use conditions and no mention of the id-vs-handle 'by' parameter interplay, so the agent must infer usage from the name alone.

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