Skip to main content
Glama
Qwinty
by Qwinty

add_objects_to_list

Add objects to a specific list in an Anytype space by providing space ID, list ID, and object IDs.

Instructions

Adds one or more objects to a specific list in a space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesSpace ID containing the list
list_idYesList ID to add objects to
object_idsYesArray of object IDs to add

Implementation Reference

  • src/index.ts:584-611 (registration)
    Registration of the 'add_objects_to_list' MCP tool, including description, Zod input schema, and inline handler function that performs a POST request to the Anytype API to add objects to a list.
    this.server.tool(
      "add_objects_to_list",
      "Adds one or more objects to a specific list in a space.",
      {
        space_id: z.string().describe("Space ID containing the list"),
        list_id: z.string().describe("List ID to add objects to"),
        object_ids: z.array(z.string()).describe("Array of object IDs to add"),
      },
      async ({ space_id, list_id, object_ids }) => {
        try {
          const response = await this.makeRequest(
            "post",
            `/spaces/${space_id}/lists/${list_id}/objects`,
            object_ids
          );
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(response.data, null, 2),
              },
            ],
          };
        } catch (error) {
          return this.handleApiError(error);
        }
      }
    );
  • Handler function that executes the tool logic: sends POST request with object_ids to /spaces/{space_id}/lists/{list_id}/objects endpoint and returns the API response.
    async ({ space_id, list_id, object_ids }) => {
      try {
        const response = await this.makeRequest(
          "post",
          `/spaces/${space_id}/lists/${list_id}/objects`,
          object_ids
        );
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return this.handleApiError(error);
      }
    }
  • Zod schema for tool inputs: space_id (string), list_id (string), object_ids (array of strings).
    {
      space_id: z.string().describe("Space ID containing the list"),
      list_id: z.string().describe("List ID to add objects to"),
      object_ids: z.array(z.string()).describe("Array of object IDs to add"),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention permissions needed, rate limits, whether duplicates are allowed, or what happens if objects are already in the list, leaving critical operational details unspecified.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured for quick understanding.

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 the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It fails to explain what the tool returns, error conditions, or side effects, leaving significant gaps in understanding how to use it effectively in context.

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. The description adds no additional meaning beyond implying that 'object_ids' are added to a list, which is redundant with the schema. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 action ('Adds') and target ('objects to a specific list in a space'), making the purpose understandable. It distinguishes from siblings like 'remove_object_from_list' by specifying addition rather than removal, though it doesn't explicitly contrast with other list-related tools.

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?

No guidance is provided on when to use this tool versus alternatives like 'create_object' or 'remove_object_from_list'. The description lacks context about prerequisites, such as whether objects must already exist or be in the same space, leaving usage unclear.

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