Skip to main content
Glama

x_api_get_spaces_buyers

Fetch the ticket buyers for a given X Space by Space ID. This read-only tool returns buyer details, useful for event organizers to manage attendees.

Instructions

Get Space ticket buyers. Use when: Get Space ticket buyers. 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: 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); pagination_token (query, unknown); max_results (query, integer). 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_buyers","arguments":{"scopeTenantId":"default","scopeUserId":"default","id":""}}

Input Schema

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

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

With no annotations provided, the description carries the full burden and excels: it declares read-only risk, required OAuth scopes, tenant/auth resolution behavior, response shape, common failure conditions, and a safety warning about sensitive data. This goes far beyond typical descriptions.

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 labeled sections (Use when, Risk, Permissions, etc.), making it scannable. It is lengthy but each section adds valuable context. The only waste is the tautological 'Use when: Get Space ticket buyers.' line.

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?

For a 9-parameter tool with no output schema, the description provides comprehensive context: response shape, failure conditions, prerequisites, environment selection, and an example. This is sufficient for an agent to invoke the tool correctly without additional resources.

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?

Since schema coverage is 0%, the description compensates by explaining id, pagination_token, max_results formats, and the behavior of scopeTenantId, scopeUserId/scopeAccountId, and credentialKey. It does not cover authorizationKey or preferredAuthType, but the schema provides an enum for the latter.

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 a clear, specific verb+resource phrase: 'Get Space ticket buyers.' This unambiguously distinguishes it from sibling tools like x_api_get_spaces_by_id, x_api_get_spaces_posts, or x_api_search_spaces.

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?

Provides a 'Do not use when' clause that names alternatives (x_schema_discovery, x_query_suggestion) and suggests prerequisite tools. However, the 'Use when' section merely restates the tool's purpose ('Get Space ticket buyers'), offering no deeper guidance on when to choose this specific tool over similar Space-focused API tools.

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