Skip to main content
Glama

List Twitter profile tweets

twitter_profile_tweets_list
Read-only

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNoTreat the path value as a handle or a numeric user id. Defaults to id when the value is all digits.
trimNoIgnored if this tool does not support it.
urlsNoAlias for `handle`. Prefer `handle`.
userNoAlias for `handle`. Prefer `handle`.
limitNoRequested page size (1–100). Best-effort; the actual page size may differ.
cursorNoOpaque pagination cursor returned by a previous response.
handleNoX (Twitter) profile handle without the leading @, or a numeric user id.
offsetNoIgnored if this tool does not support it.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
pageSizeNoIgnored if this tool does not support it.
userNameNoAlias for `handle`. Prefer `handle`.
usernameNoAlias for `handle`. Prefer `handle`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
maxResultsNoIgnored if this tool does not support it.
profileUrlNoAlias for `handle`. Prefer `handle`.
linkedinUrlNoAlias for `handle`. Prefer `handle`.
max_resultsNoIgnored if this tool does not support it.
screen_nameNoAlias for `handle`. Prefer `handle`.
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. Changed18 schema fields changed
    • addedInput schema / properties / linkedinUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / linkedinUrl / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / profileUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / profileUrl / type
      Removed value: -"string"
    • addedInput schema / properties / screen_name / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / screen_name / type
      Removed value: -"string"
    • addedInput schema / properties / trim
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / urls
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `handle`. Prefer `handle`."
      +}
    • addedInput schema / properties / user / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / user / type
      Removed value: -"string"
    • addedInput schema / properties / userName / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / userName / type
      Removed value: -"string"
    • addedInput schema / properties / username / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / username / type
      Removed value: -"string"
  2. Changed2 schema fields changed
    • addedInput schema / properties / linkedinUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / profileUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
  3. Changed10 schema fields changed
    • addedInput schema / properties / by
      Added value: +{
      +  "description": "Treat the path value as a handle or a numeric user id. Defaults to id when the value is all digits.",
      +  "enum": [
      +    "id",
      +    "handle"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / handle / description
      Previous value: -"X handle to look up, with or without a leading @."New value: +"X (Twitter) profile handle without the leading @, or a numeric user id."
    • changedInput schema / properties / includePinned / description
      Previous value: -"Include pinned tweets on the first page. Default: false."New value: +"When true, includes the pinned tweet when available."
    • changedInput schema / properties / includeReplies / description
      Previous value: -"Include reply tweets in the returned list. Default: false."New value: +"When true, includes reply tweets. Defaults to false."
    • changedInput schema / properties / limit / description
      Previous value: -"Page size (maximum 100). Default: 40."New value: +"Requested page size (1–100). Best-effort; the actual page size may differ."
    • addedInput schema / properties / screen_name
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / user
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / userName
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / username
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  4. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle"
      -]New value: +[
      +  "handle",
      +  "context",
      +  "llm_model"
      +]
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  7. Changed6 schema fields changed
    • changedInput schema / properties / includePinned / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "boolean"
      -  }
      -]New value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "enum": [
      +      "0",
      +      "1",
      +      "true",
      +      "false"
      +    ],
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / includeReplies / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "boolean"
      -  }
      -]New value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "enum": [
      +      "0",
      +      "1",
      +      "true",
      +      "false"
      +    ],
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / limit / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / limit / type
      Added value: +"integer"
  8. Changed3 schema fields changed
    • changedInput schema / properties / includePinned / description
      Previous value: -"Optional: include pinned tweets on the first page. Defaults to false."New value: +"Include pinned tweets on the first page. Default: false."
    • changedInput schema / properties / includeReplies / description
      Previous value: -"Optional: include reply tweets in the returned list. Defaults to false."New value: +"Include reply tweets in the returned list. Default: false."
    • changedInput schema / properties / limit / description
      Previous value: -"Optional page size. Defaults to 40 when omitted. Maximum supported value is 100."New value: +"Page size (maximum 100). Default: 40."
  9. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, which cover the overall safety profile. The description adds that the result is a list and that paginated responses require a cursor, but it does not disclose auth requirements, rate limits, or response item shape.

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 short sentences with the core purpose front-loaded and a useful pagination note. There is no filler, redundancy, or wasted wording.

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?

For a read-only list tool, the description, full schema coverage, and annotations provide enough to select and invoke it correctly. It would benefit from naming sibling alternatives or describing the tweet item shape since there is no output schema, but the essential invocation and pagination contract is present.

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 coverage is 100%, so the schema already documents every parameter and the baseline is 3. The description reinforces the handle/id addressing and cursor usage but does not add meaning beyond what the schema already provides.

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 clearly states the operation ('List tweets'), the resource ('X profile'), and the two addressing modes (handle or numeric user id). It does not explicitly distinguish this tool from sibling Twitter read tools, so it stops 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 Guidelines3/5

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

The description implies this tool is for retrieving a profile's tweets directly rather than searching or fetching followers, and it adds a pagination condition ('use cursor when paginated'). However, it never names a sibling alternative or states when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.