Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Twitter profile tweets

twitter_profile_tweets_list
Read-onlyIdempotent

Retrieve tweets from an X profile by handle or numeric user ID, with cursor-based pagination and options to include replies or pinned tweets.

Instructions

List tweets from an X profile by handle or numeric user id. Requires handle. Returns a list (use cursor when paginated).

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_tweets_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoTreat the path value as a handle or a numeric user id. Defaults to id when the value is all digits.
limitNoRequested page size (1–100). Best-effort; the actual page size may differ.
cursorNoOpaque pagination cursor returned by a previous response.
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.
includePinnedNoWhen true, includes the pinned tweet when available.
includeRepliesNoWhen true, includes reply tweets. Defaults to false.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds only that it returns a list and that cursor drives pagination; it omits rate-limit behavior, whether replies/pinned are included by default (that lives only in the schema), and the conversation_id sequencing requirement.

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, front-loaded with the action and resource. The 'Requires `handle`' clause is largely redundant with the schema's required list, but the overall text is tight and free of padding.

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 nine parameters, a pagination cursor, and no output schema, the return shape is described only as 'a list' — an agent cannot tell what fields each tweet object carries. The mention that cursor should be used when paginated is helpful, but the definition leaves the agent under-informed about the response and about the conversation_id handshake beyond what the schema states.

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 all nine parameters are documented in the schema itself. The description adds no syntax or format detail beyond restating that handle is required — which the schema already marks as required. Baseline 3 applies when the schema does the heavy lifting.

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+resource (list tweets from an X profile) and the two acceptable identifiers (handle or numeric user id). It does not explicitly distinguish itself from siblings like twitter_list_tweets_list or twitter_community_tweets_list, but the resource scope is unambiguous.

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?

Provides one procedural hint — use cursor when paginated — but never says when to prefer this over the list/community tweet siblings or what data is excluded. Usage is implied by the resource name rather than 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