x-mcp

X Spaces

x_spaces

Read-onlyIdempotent

Search live or scheduled audio Spaces by keyword, retrieve Space details and participant info, and read posts shared within them.

Instructions

Search live or scheduled audio Spaces and read the posts shared in them.

Actions (pass "action" plus that action's parameters):

search: Find live or scheduled audio Spaces by keyword (up to 100 results). [requires: query]
get: Fetch one Space by id: title, state, hosts, participant count and schedule. [requires: space_id]
get_many: Batch lookup of up to 100 Spaces by id. [requires: space_ids]
posts: Posts attached to a Space, 1-100 per page. [requires: space_id]

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": {
      "action": "<action>"
    },
    "name": "x_spaces"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No
`state`	No	Filter by Space state.	all
`action`	Yes	Action to perform. One of: search, get, get_many, posts.
`space_id`	No	Space id.
`space_ids`	No
`next_token`	No	Cursor from a previous response (meta.next_token).
`max_results`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds value beyond them by disclosing result caps (100 for search/get_many, 1-100 per page for posts), which tells the agent to expect bounded result sets. It omits rate limits and never mentions the next_token pagination loop, leaving the agent to discover that from the schema.

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?

Front-loaded purpose sentence followed by a compact per-action list with bracketed required params — scannable and free of filler. Every line carries information the agent needs to construct a call.

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 7-parameter, four-action tool with no output schema, the description covers action selection, required parameters per action, and result limits. The remaining gaps are the state filter and the pagination/return shape, which matter because no output schema exists to describe what comes back.

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 only 57%, and the description compensates well for the most important gap by binding each action to its required parameter (query, space_id, space_ids). It does not explain the 'state' filter, the max_results cap interplay, or pagination via next_token, so a few parameters remain documented only by 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 opening sentence names a specific resource (audio Spaces) plus the two object types it operates on (Spaces and their posts), and the action list disambiguates the four verbs. An agent can distinguish this from x_posts or x_timelines because the scope is explicitly 'live or scheduled audio Spaces' and 'posts attached to a Space'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states the calling convention ('pass action plus that action's parameters') and lists the required parameter per action, which is real routing guidance. It stops short of exclusions, e.g. it never says to use x_posts instead when you want posts outside a Space, and gives no guidance on when to use search vs get_many.

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

Deploy Server