Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitter Space stream URL

twitter_space_stream_get
Read-onlyIdempotent

Retrieve the HLS audio stream URL for an X Space using its permalink or ID, so you can access or process the Space audio.

Instructions

Get the HLS audio stream URL for an X Space by URL or id. Requires url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Space permalink or 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

B3.2/5.0
Behavior3/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's only behavioral addition is that the return value is an HLS audio stream URL, which is useful but does not mention expiry, auth requirements, geo restrictions, or behavior for ended/non-live Spaces.

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?

Two short sentences with the resource and return type front-loaded; nothing is padded. The final 'Requires `url`' clause is redundant with the schema's required array, a minor wasted sentence.

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 read-only single-resource getter with full schema coverage and four annotations, the description supplies the missing piece — what the returned value actually is (an HLS URL). It says nothing about non-live or unavailable Spaces, which is the main remaining gap.

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 baseline is 3. The description's 'by URL or id' restates what the schema already says ('Space permalink or id'), and 'Requires `url`' merely repeats the required list, so it adds essentially no new parameter meaning.

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 states a specific verb and resource ('Get the HLS audio stream URL for an X Space') and names the input domain (URL or id). This clearly separates it from the sibling twitter_space_get, which presumably returns Space metadata rather than a playable stream, though it never says so explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that this tool is for retrieving audio playback URLs rather than Space metadata, and nothing covers prerequisites or the follow-up step of playing the URL.

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