Skip to main content
Glama
Qwinty
by Qwinty

remove_object_from_list

Remove an object from a specific list in an Anytype space by specifying space, list, and object IDs.

Instructions

Removes an object from a specific list in a space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesSpace ID containing the list
list_idYesList ID to remove object from
object_idYesObject ID to remove

Implementation Reference

  • The handler function executes a DELETE request to the Anytype API endpoint to remove the specified object from the list.
    async ({ space_id, list_id, object_id }) => {
      try {
        const response = await this.makeRequest(
          "delete",
          `/spaces/${space_id}/lists/${list_id}/objects/${object_id}`
        );
        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: space_id, list_id, and object_id.
    {
      space_id: z.string().describe("Space ID containing the list"),
      list_id: z.string().describe("List ID to remove object from"),
      object_id: z.string().describe("Object ID to remove"),
    },
  • src/index.ts:614-640 (registration)
    Registration of the 'remove_object_from_list' tool using McpServer.tool(), including description, schema, and inline handler.
    this.server.tool(
      "remove_object_from_list",
      "Removes an object from a specific list in a space.",
      {
        space_id: z.string().describe("Space ID containing the list"),
        list_id: z.string().describe("List ID to remove object from"),
        object_id: z.string().describe("Object ID to remove"),
      },
      async ({ space_id, list_id, object_id }) => {
        try {
          const response = await this.makeRequest(
            "delete",
            `/spaces/${space_id}/lists/${list_id}/objects/${object_id}`
          );
          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 full burden. It states the action is 'removes,' implying a destructive mutation, but doesn't disclose behavioral traits like whether removal is permanent/reversible, permission requirements, error conditions (e.g., if object isn't in list), or what happens to the object after removal (e.g., deleted or just unlinked). This leaves significant gaps for a mutation tool.

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 with zero waste. It's front-loaded with the core action and target, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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?

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks crucial context like what 'removes' entails (e.g., permanent deletion or unlisting), expected outcomes, error handling, or permissions. Given the complexity and missing structured data, it should provide more behavioral guidance to be fully helpful.

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%, with clear descriptions for all three parameters (space_id, list_id, object_id). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or providing examples. Baseline 3 is appropriate since the 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 action ('removes') and target ('an object from a specific list in a space'), making the purpose understandable. It distinguishes from obvious siblings like 'add_objects_to_list' by specifying removal rather than addition. However, it doesn't differentiate from 'delete_object' which might delete the object entirely rather than just removing it from a list.

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 the object to be in the list first), when not to use it (e.g., vs. deleting the object entirely), or refer to sibling tools like 'delete_object' or 'add_objects_to_list' for context.

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