Skip to main content
Glama
aliyun
by aliyun

CreateDIJob

Create data integration jobs to synchronize data between various source and destination systems, supporting full, incremental, and real-time migration types with configurable transformation rules and resource settings.

Instructions

创建数据集成同步任务 *This Tool has a 'MCP Resource',please request CreateDIJob(MCP Resource) to get more examples for using this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
DestinationDataSourceTypeYes目标端数据源类型,枚举值:Hologres,OSS-HDFS,OSS,MaxCompute,LogHub,StarRocks,DataHub,AnalyticDB_For_MySQL,Kafka,Hive
SourceDataSourceTypeYes源端数据源类型,枚举值: PolarDB,MySQL,Kafka,LogHub,Hologres,Oracle,OceanBase,MongoDB,RedShift,Hive,SQLServer,Doris,ClickHouse
MigrationTypeYes同步类型,可选的枚举值有:- FullAndRealtimeIncremental(全量和实时增量,整库实时)- RealtimeIncremental(实时增量,单表实时)- Full(全量,整库离线)- OfflineIncremental(离线增量,整库离线)- FullAndOfflineIncremental(全量+离线增量,整库离线)
SourceDataSourceSettingsYes源端数据源设置列表
DestinationDataSourceSettingsYes目标端数据源设置列表
ResourceSettingsYes资源设置
TableMappingsYes同步对象转换映射列表,列表中每个元素描述了一组源端同步对象选择规则列表和在该组同步对象上应用的同步对象转换规则列表。>[{"SourceObjectSelectionRules":[{"ObjectType":"Database","Action":"Include","ExpressionType":"Exact","Expression":"biz_db"},{"ObjectType":"Schema","Action":"Include","ExpressionType":"Exact","Expression":"s1"},{"ObjectType":"Table","Action":"Include","ExpressionType":"Exact","Expression":"table1"}],"TransformationRuleNames":[{"RuleName":"my_database_rename_rule","RuleActionType":"Rename","RuleTargetType":"Schema" }]}]
DescriptionNo任务的描述
JobSettingsNo同步任务维度的设置,含DDL处理策略、源端和目标端列数据类型映射策略、任务运行时参数等
ProjectIdNoDataWorks工作空间的ID
JobNameNo该字段已废弃,请使用Name字段
NameNo任务名称
JobTypeNo任务类型,可选-DatabaseRealtimeMigration(整库实时):将源端多个库的多个表进行流同步,支持仅全量,仅增量,或全量+增量。-DatabaseOfflineMigration(整库离线):将源端多个库的多个表进行批同步,支持仅全量,仅增量,或全量+增量。-SingleTableRealtimeMigration(单表实时):将源端单个表进行流同步
TransformationRulesNo同步对象转换规则定义列表。>[{"RuleName":"my_database_rename_rule","RuleActionType":"Rename","RuleTargetType":"Schema","RuleExpression":"{\"expression\":\"${srcDatasoureName}_${srcDatabaseName}\"}"}]
Behavior1/5

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

No annotations are provided, so the description carries full burden. It only states the tool creates something, with no disclosure of behavioral traits like whether this is a configuration operation vs. immediate execution, permission requirements, rate limits, side effects, or what happens on failure. For a complex creation tool with 14 parameters, this is severely inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (two sentences) but under-specified rather than concise. The first sentence is a tautology, and the second is a meta-instruction about MCP Resources that doesn't describe the tool itself. While short, it fails to convey essential information efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex creation tool with 14 parameters, nested objects, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool actually does beyond the tautological name restatement, provides no behavioral context, and offers no guidance on usage. The comprehensive schema partially compensates but the description fails to add necessary 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%, providing detailed documentation for all 14 parameters including enumerations and examples. The description adds no parameter information beyond the schema, so it doesn't compensate but doesn't need to given the comprehensive schema. Baseline 3 is appropriate when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '创建数据集成同步任务' (Create data integration synchronization task) is a tautology that essentially restates the tool name 'CreateDIJob' in Chinese. While it indicates the tool creates something related to data integration, it lacks specificity about what exactly is being created (e.g., a job configuration, a running instance) and doesn't differentiate from potential siblings like 'CreateDISyncTask' which appears in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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, appropriate contexts, or distinguish it from other creation tools in the sibling list (e.g., 'CreateDISyncTask', 'CreateDataQualityEvaluationTask'). The second sentence about MCP Resource is a meta-instruction for tool usage examples, not a usage guideline for the tool's purpose.

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/aliyun/alibabacloud-dataworks-mcp-server'

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