Skip to main content
Glama
Qwinty

Anytype MCP Server

by Qwinty
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

export_object

Export Anytype objects to Markdown format for backup or use in external applications. Extract content for sharing or documentation purposes.

Instructions

Exports an Anytype object in Markdown format. This tool allows you to extract content from Anytype for use in other applications or for backup purposes. Markdown format is human-readable and suitable for documentation. Use this tool when you need to share Anytype content with external systems or create portable backups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesSpace ID containing the object
object_idYesObject ID to export
formatYesExport format (currently only 'markdown' is supported)

Implementation Reference

  • src/index.ts:307-334 (registration)
    Registration of the 'export_object' tool on the MCP server, including inline schema and handler function.
      "export_object",
  "Exports an Anytype object in Markdown format. This tool allows you to extract content from Anytype for use in other applications or for backup purposes. Markdown format is human-readable and suitable for documentation. Use this tool when you need to share Anytype content with external systems or create portable backups.",
  {
    space_id: z.string().describe("Space ID containing the object"),
    object_id: z.string().describe("Object ID to export"),
    format: z
      .literal("markdown")
      .describe("Export format (currently only 'markdown' is supported)"),
  },
  async ({ space_id, object_id, format }) => {
    try {
      const response = await this.makeRequest(
        "get",
        `/spaces/${space_id}/objects/${object_id}/${format}`
      );
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    } catch (error) {
      return this.handleApiError(error);
    }
  }
);
  • src/index.ts:316-333 (handler)
    The handler function for 'export_object' tool. It makes a GET request to the Anytype API endpoint `/spaces/{space_id}/objects/{object_id}/{format}` (markdown) and returns the response as JSON text content.
    async ({ space_id, object_id, format }) => {
  try {
    const response = await this.makeRequest(
      "get",
      `/spaces/${space_id}/objects/${object_id}/${format}`
    );
    return {
      content: [
        {
          type: "text" as const,
          text: JSON.stringify(response.data, null, 2),
        },
      ],
    };
  } catch (error) {
    return this.handleApiError(error);
  }
}
  • src/index.ts:309-315 (schema)
    Zod input schema for the 'export_object' tool, defining required parameters: space_id, object_id, and format (fixed to 'markdown').
    {
  space_id: z.string().describe("Space ID containing the object"),
  object_id: z.string().describe("Object ID to export"),
  format: z
    .literal("markdown")
    .describe("Export format (currently only 'markdown' is supported)"),
},

Tool Definition Quality

A3.8/5.0
Behavior3/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. It describes the tool's behavior as exporting in Markdown format for external use or backup, which is helpful. However, it lacks details on permissions required, rate limits, file size constraints, or what happens if the object doesn't exist. The description adds some behavioral context but is incomplete for a mutation-like export operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with three sentences. The first sentence front-loads the core purpose, and subsequent sentences add useful context about Markdown format and usage scenarios. There is minimal redundancy, though the second sentence slightly rephrases the first.

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

Completeness3/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 provides adequate purpose and usage context but lacks details on behavioral aspects like error handling, output format specifics (e.g., file structure), or prerequisites. For an export tool with 3 parameters and no structured safety hints, it's minimally complete but could be more informative.

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 fully documents all three parameters (space_id, object_id, format). The description does not add any parameter-specific information beyond what the schema provides (e.g., it doesn't explain format constraints further). Baseline 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 ('exports'), resource ('Anytype object'), and format ('Markdown format'). It distinguishes this tool from siblings like 'get_object_content' (which presumably retrieves content without exporting) and 'delete_object' (which removes rather than exports). The purpose is unambiguous and well-defined.

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 share Anytype content with external systems or create portable backups.' It provides clear context for usage but does not specify when NOT to use it or name specific alternatives among the sibling tools (e.g., 'get_object_content' might be an alternative for internal viewing).

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