Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitter tweet

twitter_tweet_get
Read-onlyIdempotent

Fetch a single tweet by permalink or numeric ID to retrieve its content and author profile details.

Instructions

Get a single tweet by permalink or numeric id. Requires url. Pass url (tweet permalink or numeric id); there is no id field. Author includes profile metrics when not trimmed. Warning: trim=true omits author. Credits: 1.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Tweet permalink or numeric id.
trimNoOptional: omit the author profile card and replies for a smaller response.
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.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the bar is lower; the description still adds real value with the author-profile-metrics behavior, the trim=true omission consequence, and the explicit credit cost of 1. It does not cover error behavior or return shape, but the added behavioral context is substantive.

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?

Front-loaded with the core verb and resource, and every sentence carries actionable content. The url guidance is slightly redundant ('Requires url. Pass url...; there is no id field'), repeating the same point three ways.

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 simple single-resource read with no output schema and full schema coverage, the description is close to sufficient: it covers identifier form, the trim tradeoff, and cost. Missing are hints about return contents (beyond the author card) or failure behavior on invalid ids.

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 the schema carries parameter documentation and the baseline of 3 applies. The description clarifies the url-vs-id naming confusion and the trim tradeoff, but largely restates what the schema already says about trim.

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

Purpose5/5

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

States a specific verb and resource ('Get a single tweet') and the accepted identifier form (permalink or numeric id). The word 'single' implicitly distinguishes it from the batch/related-list siblings such as twitter_tweets_batch_get and twitter_tweet_replies_list.

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?

Gives clear prerequisite-style guidance (url required, no id field) and a conditional tradeoff (trim=true omits author). However it never states when to prefer this tool over sibling list tools (e.g. replies, quotes, batch) — that routing is left to inference.

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