FMEPM Connect for Oracle EPM

Run Data Integration

run_data_integration

Destructive

Runs a named pipeline, application data load rule or integration after a preview and confirm:true. The Admin profile is required because saved jobs can affect several applications or run other steps. This pod-wide tool refuses application-restricted policies. Replace can clear existing data. Pipeline mail is disabled in the submitted variables. Custom pipeline variables use the Oracle definition. Use it after checking the saved definition, periods, import and export modes, backup and recovery plan. Check the returned id with read_data_integration, not the application job-status tool. https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/fdmee_run_data_rule.html For a write, I require a preview first, then confirm: true and its confirmationToken. The token lasts ten minutes and works once.

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": {
      "kind": "<kind>",
      "jobName": "<jobName>",
      "importMode": "<importMode>",
      "exportMode": "<exportMode>"
    },
    "name": "run_data_integration"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Saved pipeline, application data load rule or integration.
`confirm`	No	Set true after the user has approved the previewed change
`jobName`	Yes	Exact pipeline code or saved rule or integration name.
`fileName`	No	Existing Oracle inbox file for a data rule or integration. No URL.
`endPeriod`	No	Last period, for pipeline or data_rule.
`connection`	No	Connection id or label from list_connections. Defaults to the user's default connection.
`exportMode`	Yes	How to export to the application. Replace clears the selected point of view.
`importMode`	Yes	How to import source data. Choose explicitly.
`periodName`	No	Integration period expression, such as {Jan-26}{Mar-26}.
`startPeriod`	No	First Data Integration period, for pipeline or data_rule.
`confirmationToken`	No	Single-use token from this exact preview. Send it with confirm: true after the user approves. It expires after ten minutes.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already flag destructive/non-idempotent/open-world, but the description adds substantive behavior beyond them: Admin-profile authorization requirement, refusal of application-restricted policies, that Replace clears existing data, that pipeline mail is suppressed in submitted variables, that custom variables follow the Oracle definition, and the token's ten-minute single-use lifetime.

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?

Front-loaded with the core action and the preview/confirm gate, and nearly every sentence carries a distinct constraint (auth, policy refusal, mail, variables, token expiry). It is slightly dense and mixes a documentation URL and first-person phrasing ('For a write, I require...'), which costs a little polish.

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

Completeness5/5

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

For a destructive, non-idempotent 11-parameter tool with no output schema, the description covers authorization, safety gating, irreversible side effects, side-effect suppression (mail), and where to verify the returned id. An agent has everything needed to call it correctly and safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description still adds meaning by explaining that 'confirm' must be paired with a fresh preview token and that exportMode=Replace clears the point of view. It does not add much for the period/connection/fileName parameters beyond what the schema already documents.

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?

States a specific verb and resource ('Runs a named pipeline, application data load rule or integration') and enumerates exactly the three selectable kinds, which separates it from siblings like run_business_rule, run_change and epm_rest_run_job. It also names read_data_integration as the status-check counterpart and explicitly says not to use the application job-status tool.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit sequencing rule (preview first, then confirm:true with the preview's confirmationToken), prerequisites (Admin profile, policies that are not application-restricted), and pre-flight checks (saved definition, periods, import/export modes, backup plan). It also names the correct follow-up tool versus the wrong one, which is unusually complete routing guidance.

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

All FMEPM Connect for Oracle EPM tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?