Skip to main content
Glama

List Histories

affine_list_histories

Retrieve document history timestamps for a specific document in AFFiNE workspaces, enabling version tracking and audit trail management.

Instructions

List doc histories (timestamps) for a doc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
beforeNo
guidYes
takeNo
workspaceIdNo

Implementation Reference

  • The handler function that executes the tool logic: queries the GraphQL API for document histories in a workspace, given guid, optional take and before parameters.
    const listHistoriesHandler = async (parsed: { workspaceId?: string; guid: string; take?: number; before?: string }) => {
      const workspaceId = parsed.workspaceId || defaults.workspaceId || parsed.workspaceId;
      if (!workspaceId) throw new Error("workspaceId required (or set AFFINE_WORKSPACE_ID)");
      const query = `query Histories($workspaceId:String!,$guid:String!,$take:Int,$before:DateTime){ workspace(id:$workspaceId){ histories(guid:$guid, take:$take, before:$before){ id timestamp workspaceId } } }`;
      const data = await gql.request<{ workspace: any }>(query, { workspaceId, guid: parsed.guid, take: parsed.take, before: parsed.before });
      return text(data.workspace.histories);
    };
  • Registers the 'affine_list_histories' tool with the MCP server, providing title, description, input schema, and linking to the handler function.
    server.registerTool(
      "affine_list_histories",
      {
        title: "List Histories",
        description: "List doc histories (timestamps) for a doc.",
        inputSchema: {
          workspaceId: z.string().optional(),
          guid: z.string(),
          take: z.number().optional(),
          before: z.string().optional()
        }
      },
      listHistoriesHandler as any
    );
  • Zod-based input schema defining parameters for the tool: optional workspaceId, required guid, optional take and before.
    inputSchema: {
      workspaceId: z.string().optional(),
      guid: z.string(),
      take: z.number().optional(),
      before: z.string().optional()
    }
  • src/index.ts:68-68 (registration)
    Top-level call to registerHistoryTools, which in turn registers the 'affine_list_histories' tool among others.
    registerHistoryTools(server, gql, { workspaceId: config.defaultWorkspaceId });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't specify permissions required, rate limits, pagination details, or what the output format looks like. This is inadequate for a tool with 4 parameters and no output schema.

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 wasted words. It's front-loaded with the core purpose, making it easy to parse quickly.

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 4 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain parameter usage, output format, or behavioral constraints, leaving significant gaps for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It only mentions 'guid' implicitly ('for a doc'), leaving 'before', 'take', and 'workspaceId' completely unexplained. This fails to add meaningful semantics beyond the bare schema.

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 ('List') and resource ('doc histories (timestamps) for a doc'), making the purpose specific and understandable. However, it doesn't distinguish this tool from potential sibling tools like 'list_docs' or 'recent_docs' that might also list document-related information, preventing a perfect score.

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 any prerequisites, exclusions, or compare it to sibling tools such as 'list_docs' or 'recent_docs', leaving the agent without context for selection.

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

Related 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/DAWNCR0W/affine-mcp-server'

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