Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

update-pipeline

Modify a pipeline in OpenMetadata by applying JSON Patch operations to update fields such as description or other attributes.

Instructions

Update a pipeline using JSON Patch operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPipeline UUID to update
operationsYesJSON Patch operations array (e.g. [{op:'add', path:'/description', value:'...'}])

Implementation Reference

  • The handler function for the update-pipeline tool. It asserts write permissions are enabled, then sends a PATCH request to `/pipelines/{id}` with JSON Patch operations.
    export async function updatePipeline(params: z.infer<typeof updatePipelineSchema>) {
      assertWriteAllowed();
      return omClient.patch(`/pipelines/${params.id}`, params.operations);
    }
  • Zod schema defining the input for update-pipeline: requires a pipeline UUID (id) and an array of JSON Patch operations.
    export const updatePipelineSchema = z.object({
      id: z.string().describe("Pipeline UUID to update"),
      operations: z.array(z.record(z.string(), z.any())).describe("JSON Patch operations array (e.g. [{op:'add', path:'/description', value:'...'}])"),
    });
  • src/index.ts:278-278 (registration)
    Registration of the update-pipeline tool with the MCP server: name, description, schema shape, and wrapped handler.
    tool("update-pipeline", "Update a pipeline using JSON Patch operations", updatePipelineSchema.shape, wrapToolHandler(updatePipeline));
  • Helper function called by the handler to check if write operations are allowed before making the API call.
    export function assertWriteAllowed(): void {
      if (!config.allowWrite) {
        throw new WriteBlockedError();
      }
    }
  • The wrapToolHandler utility that wraps the handler function to provide error handling and redaction.
    export const wrapToolHandler = createWrapToolHandler({
      redactionPatterns: [/OPENMETADATA_TOKEN/i],
      errorExtractors: [
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It indicates mutation ('update') but fails to disclose details such as partial update behavior, error states, authorization needs, or return values. This is insufficient 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, concise sentence that is front-loaded with the key information. Every word earns its place with no redundancy or filler.

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 the simplicity of the tool (2 parameters, no output schema), the description is minimally adequate. However, it lacks detail on return values or side effects, leaving some gaps in completeness for an agent to rely on solely.

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 coverage is 100% with clear descriptions for both parameters. The description adds the phrase 'using JSON Patch operations' which reinforces the operations schema but does not significantly enhance meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 verb 'update' and the resource 'pipeline', and specifies the method 'JSON Patch operations'. It distinguishes from sibling tools like 'create-pipeline' and 'delete-pipeline' by focusing on updating an existing pipeline.

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 over alternatives, nor does it mention prerequisites, limitations, or context for usage. It is a bare statement without usage context.

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/us-all/openmetadata-mcp-server'

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