Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Twitter Space

twitter_space_get
Read-onlyIdempotent

Retrieve details for an X Space audio room by permalink or ID, letting agents fetch space metadata directly from a given URL.

Instructions

Get an X Space (audio room) 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_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.1/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 fully covered. The description's only added context is the definition of a Space as an audio room and the accepted key forms. It says nothing about what is returned, whether private/suspended Spaces fail, or rate-limit behavior.

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 action first and the prerequisite second; no filler, no redundancy beyond the minor restatement of the url requirement.

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?

This is a simple single-resource getter with a fully documented schema, so the description is close to sufficient. However, with no output schema present, an agent gets no sense of what a retrieved Space object contains or in what shape it arrives, which is the one remaining informational gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the url property already reads "Required. Space permalink or id." The description's "by URL or id" and "Requires `url`" merely repeat that text. No added meaning is given for permalink format versus numeric id, nor any mention of the context, llm_model, or conversation_id parameters.

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 and resource ("Get an X Space") and explains what a Space is ("audio room"), which an agent may not otherwise know. It also says the lookup key can be a URL or id. It stops short of differentiating itself from siblings such as twitter_space_stream_get, which also operate on Spaces.

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 only guidance is the prerequisite "Requires `url`", which is already enforced by the schema's required list. There is no statement of when to prefer this tool over twitter_space_stream_get or other *_get siblings, and no exclusions or error conditions are mentioned.

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