Skip to main content
Glama
Sign In

TwittrAPI

by io.github.twittrapi
OverviewDiscussionsAdmin

Get Space

get_space
Read-onlyIdempotent

Get an X Space by ID: title, state, host and participants, and whether a replay is available. Returns raw JSON.

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": {
      "spaceId": "<spaceId>"
    },
    "name": "get_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceIdYesSpace ID, the letters and digits at the end of the Space URL (x.com/i/spaces/<spaceId>).
max_charsNoMaximum characters of JSON to return (default 50000). Longer output is cut with a [TRUNCATED] marker. Lower it to save context, raise it if you need the full response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 adds modest value by saying the result is raw JSON and listing the fields, but it says nothing about lookup failures, deleted Spaces, or output truncation behavior. With annotations doing the heavy lifting, a 3 is appropriate.

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, front-loaded with the action and resource, then the return contents. Every clause carries information and nothing is redundant.

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?

There is no output schema, so the field enumeration (title, state, host, participants, replay availability) is genuinely necessary and present. The remaining gaps are minor for a simple two-parameter read tool: error behavior for nonexistent or non-Space IDs is unstated, and truncation is left entirely to the schema.

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

Parameters4/5

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

Schema coverage is 100% and the spaceId description already explains the URL-derived format, so the baseline would be 3. The description's "by ID" phrasing reinforces which identifier is required, and "Returns raw JSON" gives context for the max_chars truncation parameter, adding a small amount of meaning beyond the schema.

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?

The description gives a specific verb and resource ("Get an X Space by ID") and then enumerates what the agent will receive: title, state, host, participants, and replay availability. There is no sibling tool in the provided list that also handles Spaces, so the scope is unambiguous without needing explicit differentiation.

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?

Usage is only implied: an agent should call this when it already has a Space ID and wants details. There is no statement of when not to use it, no mention of what happens with an invalid or expired ID, and no routing to alternatives, though no obvious alternative exists among the siblings.

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

All TwittrAPI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources