Cloudera Data Visualization MCP Server

create_extract

Create a data extract job that moves data from a source dataset to a target database table, applying dimension and aggregate columns.

Instructions

Create a CDV data extract job.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "src_dataset_id": "<src_dataset_id>",
      "tgt_dataconnection_id": "<tgt_dataconnection_id>",
      "tgt_dbname": "<tgt_dbname>",
      "tgt_tablename": "<tgt_tablename>",
      "dim_data": "<dim_data>",
      "agg_data": "<agg_data>"
    },
    "name": "create_extract"
  }
}

Input Schema

Name	Required	Description	Default
`src_dataset_id`	Yes	Source dataset ID.
`tgt_dataconnection_id`	Yes	Target data connection ID.
`tgt_dbname`	Yes	Target database name.
`tgt_tablename`	Yes	Target table name.
`dim_data`	Yes	JSON string of dimension columns, e.g. '[{"expr":"[col]","alias":"col"}]'.
`agg_data`	Yes	JSON string of aggregate columns, e.g. '[{"expr":"sum([col])","alias":"col"}]'.
`partition_data`	No	JSON string of partition columns for incremental refresh (default '[]').	[]
`schedule_id`	No	Optional schedule ID to attach a job to the extract.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states a vague action, failing to mention side effects, return value (though output schema exists), or whether the job is created and then run separately.

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 a single, efficient sentence with no redundancy. However, it may be too terse given the tool's complexity and lack of annotations.

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?

Despite an output schema existing, the description fails to provide essential context about the tool's operation, such as what a CDV data extract is, how it integrates with other tools, or typical workflow steps.

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%, so each parameter is already described. The description adds no extra meaning beyond the schema, meriting a baseline score of 3.

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 it creates a CDV data extract job, using a specific verb and resource. It distinguishes from sibling 'create_' tools by specifying 'CDV data extract', but does not elaborate on what a CDV data extract is.

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?

No guidance on when to use this tool versus alternatives like run_extract or other create tools. The description lacks context on prerequisites or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server