Skip to main content
Glama

anytype_delete_property

Remove a property from an Anytype object by specifying the space ID and property ID. This tool deletes custom properties to clean up object structures.

Instructions

Elimina una propiedad

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesID del espacio
property_idYesID de la propiedad

Implementation Reference

  • The main handler function that destructures the input arguments, validates required parameters (space_id and property_id), and sends a DELETE request to the Anytype API endpoint `/v1/spaces/{space_id}/properties/{property_id}` to delete the property. Returns the API response as text content.
    export async function handleDeleteProperty(args: any) {
      const { space_id, property_id } = args;
      
      if (!space_id || !property_id) {
        return { 
          content: [{ 
            type: 'text', 
            text: JSON.stringify({
              error: 'Missing required parameters',
              message: 'Fields "space_id" and "property_id" are required for deleting a property',
              provided_parameters: Object.keys(args)
            }, null, 2) 
          }] 
        };
      }
      
      const response = await makeRequest(`/v1/spaces/${space_id}/properties/${property_id}`, {
        method: 'DELETE',
      });
      return { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] };
    }
  • The schema definition for the 'anytype_delete_property' tool within the propertyTools array, defining the input schema with required string parameters space_id and property_id.
    {
      name: 'anytype_delete_property',
      description: 'Elimina una propiedad',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'ID del espacio' },
          property_id: { type: 'string', description: 'ID de la propiedad' },
        },
        required: ['space_id', 'property_id'],
      },
    },
  • src/index.ts:144-145 (registration)
    The switch case in the CallToolRequest handler that routes calls to 'anytype_delete_property' to the handleDeleteProperty function.
    case 'anytype_delete_property':
      return await handleDeleteProperty(args);
  • src/index.ts:46-52 (registration)
    The import statement in src/index.ts that brings in the handleDeleteProperty handler from src/handlers/properties.ts.
    import {
      handleListProperties,
      handleGetProperty,
      handleCreateProperty,
      handleUpdateProperty,
      handleDeleteProperty
    } from './handlers/properties.js';
  • src/index.ts:17-88 (registration)
    The import of propertyTools (containing the tool schema) and its inclusion in the combined tools list used for ListToolsRequest in the MCP server.
    import { propertyTools } from './tools/properties.js';
    import { typeTools } from './tools/types.js';
    import { tagTools } from './tools/tags.js';
    import { templateTools } from './tools/templates.js';
    import { listTools } from './tools/lists.js';
    
    // Import handlers
    import {
      handleListSpaces,
      handleGetSpace,
      handleCreateSpace,
      handleUpdateSpace,
      handleListMembers,
      handleGetMember
    } from './handlers/spaces.js';
    
    import {
      handleSearchObjects,
      handleListObjects,
      handleGetObject,
      handleCreateObject,
      handleUpdateObject,
      handleDeleteObject,
      handleAddToCollection,
      handleRemoveFromCollection,
      handleGetListViews,
      handleGetListObjects
    } from './handlers/objects.js';
    
    import {
      handleListProperties,
      handleGetProperty,
      handleCreateProperty,
      handleUpdateProperty,
      handleDeleteProperty
    } from './handlers/properties.js';
    
    import {
      handleListTypes,
      handleGetType,
      handleCreateType,
      handleUpdateType,
      handleDeleteType,
      handleListTags,
      handleGetTag,
      handleCreateTag,
      handleUpdateTag,
      handleDeleteTag,
      handleListTemplates,
      handleGetTemplate
    } from './handlers/types-tags.js';
    
    console.error('API Key:', process.env.ANYTYPE_API_KEY ? 'Present' : 'Missing');
    
    // Create the server
    const server = new Server(
      {
        name: 'anytype-mcp-server',
        version: '0.1.0',
      },
      {
        capabilities: {
          tools: {},
        },
      }
    );
    
    // Combine all tools from modules
    const tools = [
      ...spaceTools,
      ...objectTools,
      ...propertyTools,
Behavior1/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 only states the action ('Elimina') without disclosing behavioral traits like whether deletion is permanent, requires specific permissions, affects related objects, or has side effects (e.g., data loss). For a destructive operation with zero annotation coverage, this is a critical gap.

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 ('Elimina una propiedad') with zero wasted words. It is appropriately sized for a simple action, though its brevity contributes to gaps in other dimensions. No structural issues are present.

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 tool's complexity (a destructive operation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address key aspects like return values, error conditions, or safety considerations, leaving significant gaps for an AI agent to understand the tool's behavior.

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?

The input schema has 100% description coverage, with clear parameter descriptions ('ID del espacio', 'ID de la propiedad'). The tool description adds no additional meaning beyond the schema, such as explaining what a 'property' entails or format examples. With high schema coverage, the baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'Elimina una propiedad' (Deletes a property) states the basic action but is tautological with the tool name 'anytype_delete_property'. It doesn't specify what kind of property (e.g., object property, space property) or distinguish it from sibling tools like 'anytype_delete_object' or 'anytype_delete_tag'. The purpose is clear at a surface level but lacks differentiation.

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

Usage Guidelines1/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. With siblings like 'anytype_delete_object', 'anytype_delete_tag', and 'anytype_delete_type', the description doesn't clarify the specific context for property deletion, such as prerequisites (e.g., property must exist) or exclusions (e.g., cannot delete system properties).

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

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