Skip to main content
Glama
Qwinty
by Qwinty

get_space_members

Retrieve a list of members with access to an Anytype space, including their IDs, names, and permission levels. Use this tool to view collaborators and manage space access permissions.

Instructions

Retrieves a list of all members who have access to a specified Anytype space. This tool provides information about each member including their ID, name, and access level. Results are paginated for spaces with many members. Use this tool when you need to understand who has access to a space or manage collaboration permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesSpace ID to get members from
offsetNoPagination offset
limitNoNumber of results per page (1-1000)

Implementation Reference

  • The handler function for the 'get_space_members' tool. It validates the limit parameter, makes a GET request to the Anytype API endpoint `/spaces/${space_id}/members` with pagination parameters, and returns the JSON response or handles errors using the shared error handler.
    async ({ space_id, offset, limit }) => {
      try {
        // Validate limit
        const validLimit = Math.max(1, Math.min(1000, limit));
    
        const response = await this.makeRequest(
          "get",
          `/spaces/${space_id}/members`,
          null,
          { offset, limit: validLimit }
        );
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return this.handleApiError(error);
      }
    }
  • Zod schema defining the input parameters for the 'get_space_members' tool: space_id (required string), offset (optional number, default 0), limit (optional number, default 100).
    {
      space_id: z.string().describe("Space ID to get members from"),
      offset: z.number().optional().default(0).describe("Pagination offset"),
      limit: z
        .number()
        .optional()
        .default(100)
        .describe("Number of results per page (1-1000)"),
    },
  • src/index.ts:337-372 (registration)
    The complete registration of the 'get_space_members' tool using this.server.tool(), including the tool name, description, input schema, and inline handler function.
    this.server.tool(
      "get_space_members",
      "Retrieves a list of all members who have access to a specified Anytype space. This tool provides information about each member including their ID, name, and access level. Results are paginated for spaces with many members. Use this tool when you need to understand who has access to a space or manage collaboration permissions.",
      {
        space_id: z.string().describe("Space ID to get members from"),
        offset: z.number().optional().default(0).describe("Pagination offset"),
        limit: z
          .number()
          .optional()
          .default(100)
          .describe("Number of results per page (1-1000)"),
      },
      async ({ space_id, offset, limit }) => {
        try {
          // Validate limit
          const validLimit = Math.max(1, Math.min(1000, limit));
    
          const response = await this.makeRequest(
            "get",
            `/spaces/${space_id}/members`,
            null,
            { offset, limit: validLimit }
          );
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(response.data, null, 2),
              },
            ],
          };
        } catch (error) {
          return this.handleApiError(error);
        }
      }
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully describes key behavioral traits: that results are paginated (important for handling large datasets), and it implies this is a read-only operation by using 'retrieves' and 'provides information'. However, it doesn't mention potential rate limits, authentication requirements, or error conditions.

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?

The description is efficiently structured in three sentences: purpose statement, details about returned information, and usage guidance. Every sentence adds value - the first establishes core functionality, the second adds important behavioral context (pagination), and the third provides application guidance. No wasted words or redundancy.

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 read operation with no output schema, the description provides good context: it explains what information is returned (ID, name, access level), mentions pagination behavior, and gives usage guidance. However, without annotations or output schema, it could benefit from more detail about return format structure or error handling. The 100% schema coverage helps compensate for some gaps.

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?

With 100% schema description coverage, the schema already documents all three parameters thoroughly. The description doesn't add any additional parameter semantics beyond what's in the schema - it doesn't explain space_id format, offset/limit usage patterns, or provide examples. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 clearly states the specific action ('retrieves a list of all members'), identifies the resource ('specified Anytype space'), and distinguishes it from siblings by focusing on space membership rather than objects, spaces, or search operations. It goes beyond the tool name by specifying what information is provided about each member.

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 explicitly states when to use this tool ('when you need to understand who has access to a space or manage collaboration permissions'), providing clear context for its application. However, it doesn't specify when NOT to use it or mention alternatives among the sibling tools (like whether get_spaces or search_space might be related alternatives).

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/Qwinty/anytype-mcp'

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