Skip to main content
Glama
Qwinty
by Qwinty

get_list_view_objects

Retrieve filtered and sorted objects from a specific list view in Anytype using space, list, and view identifiers with pagination support.

Instructions

Retrieves objects from a specific list view with applied filters and sorting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesSpace ID containing the list
list_idYesList ID
view_idYesView ID
offsetNoPagination offset
limitNoNumber of results per page (1-1000)

Implementation Reference

  • Handler function that retrieves objects from a specific list view by making an authenticated GET request to the Anytype API endpoint `/spaces/{space_id}/lists/{list_id}/{view_id}/objects` with pagination parameters.
      async ({ space_id, list_id, view_id, offset, limit }) => {
        try {
          const validLimit = Math.max(1, Math.min(1000, limit));
          const response = await this.makeRequest(
            "get",
            `/spaces/${space_id}/lists/${list_id}/${view_id}/objects`,
            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_list_view_objects tool: space_id, list_id, view_id (required strings), offset and limit (optional numbers with defaults).
      space_id: z.string().describe("Space ID containing the list"),
      list_id: z.string().describe("List ID"),
      view_id: z.string().describe("View ID"),
      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:546-581 (registration)
    MCP server tool registration call that registers the get_list_view_objects tool with name, description, input schema, and handler function.
    this.server.tool(
      "get_list_view_objects",
      "Retrieves objects from a specific list view with applied filters and sorting.",
      {
        space_id: z.string().describe("Space ID containing the list"),
        list_id: z.string().describe("List ID"),
        view_id: z.string().describe("View ID"),
        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, list_id, view_id, offset, limit }) => {
        try {
          const validLimit = Math.max(1, Math.min(1000, limit));
          const response = await this.makeRequest(
            "get",
            `/spaces/${space_id}/lists/${list_id}/${view_id}/objects`,
            null,
            { offset, limit: validLimit }
          );
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(response.data, null, 2),
              },
            ],
          };
        } catch (error) {
          return this.handleApiError(error);
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'retrieves' which implies a read-only operation, but doesn't clarify permissions, rate limits, pagination behavior beyond the schema, or what happens with invalid inputs. For a tool with 5 parameters and no annotations, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core action ('retrieves objects') and adds necessary qualifiers ('from a specific list view with applied filters and sorting'). There is zero waste, and it's appropriately sized for the tool's complexity.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool with 5 parameters. It doesn't explain the return format, error conditions, or behavioral nuances like how filters/sorting are applied. For a retrieval tool in a context with many siblings, more guidance is needed to ensure correct usage.

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?

Schema description coverage is 100%, so the schema already documents all parameters (space_id, list_id, view_id, offset, limit). The description adds minimal value by mentioning 'filters and sorting' but doesn't explain how these relate to the parameters or provide additional context beyond the schema. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'retrieves' and the resource 'objects from a specific list view', making the purpose understandable. It specifies that filters and sorting are applied, which distinguishes it from generic retrieval tools like 'get_objects'. However, it doesn't explicitly differentiate from 'get_list_views' (which likely retrieves views rather than objects), leaving some sibling distinction incomplete.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a list view setup), exclusions, or compare it to sibling tools like 'get_objects' (which might retrieve objects without view filters) or 'global_search'. Usage is implied by the name but not explicitly stated.

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