Skip to main content
Glama

x_api_get_spaces_by_id

Retrieves a specific X Space by its unique ID. Uses scoped credentials for authenticated, read-only access to Space details.

Instructions

Get space by ID. Use when: Get space by ID. Do not use when: a more specific auth/configuration tool is required before the API call or you are only exploring; prefer x_schema_discovery or x_query_suggestion first. Risk: read-only. Required permissions and prerequisites: bearer token; OAuth 2 user token with scopes space.read, tweet.read, users.read Environment-selection behavior: scopeTenantId plus exactly one of scopeUserId or scopeAccountId choose the Vault/Postgres tenant principal used for auth resolution. credentialKey selects a non-default stored credential profile when present. Parameter formats and constraints: id (path, string, required). Expected response shape: { ok, status, data: { method, path, url, status, contentType, authType, data } } Common failure conditions: missing scoped credentials in Vault, missing required API parameters, X API auth failures, rate limits, or unsupported multipart/body shape. Recommended prerequisite and follow-up tools: x_connection_info, x_schema_discovery, x_auth_get_scope_credentials, x_api_request. Safety warnings: This is read-only, but responses can still include sensitive account data depending on granted scopes. Example: {"name":"x_api_get_spaces_by_id","arguments":{"scopeTenantId":"default","scopeUserId":"default","id":""}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
scopeUserIdNo
credentialKeyNo
scopeTenantIdNo
scopeAccountIdNo
authorizationKeyNo
preferredAuthTypeNo
Behavior5/5

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

No annotations are provided, so the description carries full responsibility. It discloses read-only risk, sensitive data warnings, required permissions (bearer token and OAuth 2 scopes), environment-selection behavior, expected response shape, common failure conditions, and safety warnings. This is comprehensive behavioral disclosure.

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?

The description is well-structured with clear section labels and flows logically. It is longer than the 1-2 sentence ideal, but the length is justified by the tool's complexity and lack of annotations. Some redundancy exists ("Use when: Get space by ID" repeats the purpose), but overall it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, no annotations, no output schema), the description is remarkably complete. It covers purpose, usage, permissions, response shape, failure conditions, prerequisites, follow-up tools, safety, and an example. The expected response shape compensates for the missing output schema.

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?

The schema has 0% description coverage, and the description explains some parameters (scopeTenantId, scopeUserId/scopeAccountId, credentialKey) through environment-selection behavior. However, it does not explain authorizationKey or preferredAuthType, and only id is listed in the parameter formats section. The description adds meaning but is incomplete for all seven parameters.

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 opens with "Get space by ID," a specific verb and resource that clearly states the tool's function. It differentiates from sibling tools by the singular ID focus (e.g., x_api_get_spaces_by_ids) and includes a usage directive. The purpose is unambiguous.

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?

The description provides explicit "Use when" and "Do not use when" sections, including alternatives like preferring x_schema_discovery or x_query_suggestion for exploration. It also lists recommended prerequisite and follow-up tools. The "Use when" phrasing is tautological but the additional guidance is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LesterAJohn/X-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server