Skip to main content
Glama
DumplingAI

Dumpling AI MCP Server

Official
by DumplingAI

write-pdf-metadata

Add or modify metadata like title, author, and keywords in PDF files using URL or base64 input to organize and categorize documents.

Instructions

Write metadata to PDF files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputMethodYesInput method
filesYesArray of URLs or base64-encoded PDFs
metadataYesMetadata to write

Implementation Reference

  • The handler function that implements the tool logic by proxying requests to the external Dumpling AI API endpoint for writing PDF metadata.
    async ({ inputMethod, files, metadata }) => {
      const apiKey = process.env.DUMPLING_API_KEY;
      if (!apiKey) throw new Error("DUMPLING_API_KEY not set");
      const response = await fetch(`${NWS_API_BASE}/api/v1/write-pdf-metadata`, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          Authorization: `Bearer ${apiKey}`,
        },
        body: JSON.stringify({ inputMethod, files, metadata }),
      });
      if (!response.ok)
        throw new Error(`Failed: ${response.status} ${await response.text()}`);
      const data = await response.json();
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
  • Input schema defined using Zod for validating the tool parameters: inputMethod, files, and metadata object.
    {
      inputMethod: z.enum(["url", "base64"]).describe("Input method"),
      files: z.array(z.string()).describe("Array of URLs or base64-encoded PDFs"),
      metadata: z
        .object({
          Title: z.string().optional(),
          Author: z.string().optional(),
          Subject: z.string().optional(),
          Keywords: z.string().optional(),
          Creator: z.string().optional(),
          Producer: z.string().optional(),
        })
        .describe("Metadata to write"),
    },
  • src/index.ts:821-854 (registration)
    The server.tool call that registers the 'write-pdf-metadata' tool with MCP server, including name, description, schema, and handler.
    server.tool(
      "write-pdf-metadata",
      "Write metadata to PDF files.",
      {
        inputMethod: z.enum(["url", "base64"]).describe("Input method"),
        files: z.array(z.string()).describe("Array of URLs or base64-encoded PDFs"),
        metadata: z
          .object({
            Title: z.string().optional(),
            Author: z.string().optional(),
            Subject: z.string().optional(),
            Keywords: z.string().optional(),
            Creator: z.string().optional(),
            Producer: z.string().optional(),
          })
          .describe("Metadata to write"),
      },
      async ({ inputMethod, files, metadata }) => {
        const apiKey = process.env.DUMPLING_API_KEY;
        if (!apiKey) throw new Error("DUMPLING_API_KEY not set");
        const response = await fetch(`${NWS_API_BASE}/api/v1/write-pdf-metadata`, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            Authorization: `Bearer ${apiKey}`,
          },
          body: JSON.stringify({ inputMethod, files, metadata }),
        });
        if (!response.ok)
          throw new Error(`Failed: ${response.status} ${await response.text()}`);
        const data = await response.json();
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Write metadata' implies a mutation operation, but it doesn't disclose whether this overwrites existing metadata, requires specific permissions, handles errors, or has side effects. The description lacks critical behavioral context for a write operation.

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 action and resource, making it immediately scannable and appropriately sized for the tool's complexity.

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 inadequate. It doesn't explain what happens after writing metadata (e.g., success/failure responses, file modifications), nor does it cover behavioral aspects like error handling or limitations. The context demands more completeness for safe agent use.

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 all parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema, such as explaining metadata field formats or file handling. 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 verb ('Write') and resource ('metadata to PDF files'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'read-pdf-metadata' or 'merge-pdfs', but the action is specific enough to understand what it does.

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 like 'read-pdf-metadata' or 'merge-pdfs'. There's no mention of prerequisites, limitations, or typical use cases, leaving the agent to infer usage from context alone.

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/DumplingAI/mcp-server-dumplingai'

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