Skip to main content
Glama

FMEPM Connect for Oracle EPM

Export job history

export_job_history
Destructive

Creates a job-console export file in Oracle. This writes a file and needs a preview first, then confirm:true. It includes every job type and status, including failures, and excludes error-log contents. Check the returned job with check_job_status, then read the file with list_recent_jobs. Oracle requires Service Administrator, Job - Manage or Job - View access. Use it to prepare a fresh job-history file. https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/pbcs_export_job_console_job.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": {
      "fileName": "<fileName>"
    },
    "name": "export_job_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoExport the last 1, 2, 7, 30 or 60 days, or All.7
confirmNoSet true after the user has approved the previewed change
fileNameYesExisting outbox file name, or the new name for an export. No path or URL.
connectionNoConnection id or label from list_connections. Defaults to the user's default connection.
applicationNoApplication name. Defaults to the chosen connection.
confirmationTokenNoSingle-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.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already flag destructive/write behavior, but the description adds substantial context beyond them: the two-step preview→confirm handshake, single-use ten-minute confirmationToken, required Oracle privileges (Service Administrator, Job - Manage or Job - View), and the exact scope of exported data including failures but excluding error logs. This is exactly the operational detail an agent needs for a destructive, non-idempotent call.

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 purpose and scope are front-loaded, but the preview/confirm requirement is stated twice ('needs a preview first, then confirm:true' and again as 'For a write, I require a preview first, then confirm: true and its confirmationToken'), and the first-person 'I require' phrasing plus the inline docs URL add clutter. The repetition costs it a point.

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

Completeness4/5

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

For a destructive write tool with no output schema, the description covers permissions, content scope, the confirmation handshake and how to follow up via check_job_status and list_recent_jobs. The only gap is what the call itself returns (job id vs. file reference), which is implied by 'the returned job' but not stated.

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 all six parameters including the days enum, fileName pattern and token lifetime are already documented in structured fields. The description restates the confirm/token flow but adds no new syntax, format or default behavior beyond what the schema provides, so baseline 3 applies.

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 — 'Creates a job-console export file in Oracle' — and immediately scopes the content ('every job type and status, including failures, and excludes error-log contents'). This distinguishes it from export_data, export_metadata, export_access_report and list_recent_jobs without requiring the schema.

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

Usage Guidelines4/5

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

Gives an explicit use case ('prepare a fresh job-history file') and a downstream workflow: preview first, then confirm:true, then check_job_status, then list_recent_jobs to read the file. It does not explicitly exclude alternatives (e.g., when to use list_recent_jobs alone instead of exporting), so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources