Skip to main content
Glama

quip_append_content

Add new content to existing Quip documents by appending markdown text to specified document threads.

Instructions

Append content to an existing Quip document

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadIdYesThe Quip document thread ID
contentYesMarkdown content to append to the document

Implementation Reference

  • Handler for the 'quip_append_content' tool: validates arguments and calls editDocument with 'APPEND' operation to append content to a Quip document.
    case 'quip_append_content': {
      const typedArgs = args as any;
      if (!typedArgs.threadId || !typedArgs.content) {
        throw new McpError(ErrorCode.InvalidParams, 'threadId and content are required');
      }
      return await this.editDocument(String(typedArgs.threadId), String(typedArgs.content), 'APPEND');
    }
  • src/index.ts:66-82 (registration)
    Registration of the 'quip_append_content' tool in the listTools response, including name, description, and input schema.
      name: 'quip_append_content',
      description: 'Append content to an existing Quip document',
      inputSchema: {
        type: 'object',
        properties: {
          threadId: {
            type: 'string',
            description: 'The Quip document thread ID'
          },
          content: {
            type: 'string',
            description: 'Markdown content to append to the document'
          }
        },
        required: ['threadId', 'content'],
      },
    },
  • Helper method that implements the core logic for editing Quip documents (used by append, prepend, replace): writes content to temp file and executes quip_edit.py script.
    private async editDocument(threadId: string, content: string, operation: string) {
      try {
        console.log(`Editing document ${threadId} with operation ${operation}...`);
        
        // Create a temporary file to store the content
        const tempFilePath = `/tmp/quip_content_${Date.now()}.md`;
        const writeCommand = `echo "${content.replace(/"/g, '\\"')}" > ${tempFilePath}`;
        await execAsync(writeCommand);
        
        // Execute the Python script to edit the document
        const command = `python -u ${path.join(SCRIPTS_DIR, 'quip_edit.py')} ${threadId} ${operation.toLowerCase()} ${tempFilePath}`;
        const { stdout, stderr } = await execAsync(command);
        
        // Clean up the temporary file
        await execAsync(`rm ${tempFilePath}`);
        
        if (stderr) {
          console.error(`Error editing document: ${stderr}`);
          throw new Error(stderr);
        }
    
        return {
          content: [
            {
              type: 'text',
              text: stdout || `Successfully ${operation.toLowerCase()}ed content to document ${threadId}`,
            },
          ],
        };
      } catch (error) {
        console.error(`Error ${operation.toLowerCase()}ing document:`, error);
        throw error;
      }
    }
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 the action ('Append content') but lacks details on permissions required, whether the operation is idempotent, how content is formatted (beyond markdown in schema), error conditions, or what happens if the threadId is invalid. 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 that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, error handling, or return values, which are critical for an agent to use this tool effectively. The high schema coverage doesn't compensate for these gaps 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 both parameters (threadId and content) adequately. The description adds no additional meaning beyond implying that content is appended to a document, which is redundant with the tool name. This meets the baseline for high schema coverage.

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 ('Append content') and target resource ('to an existing Quip document'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'quip_prepend_content' or 'quip_replace_content' beyond the verb 'append', which slightly limits its distinctiveness.

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 an existing document), exclusions, or comparisons to siblings like 'quip_prepend_content' or 'quip_replace_content', leaving the agent to infer usage context solely from the tool name.

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/AvinashBole/quip-mcp-server'

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