mcp-fabric-api

copy_job_get

Read-only

Get details of a specific copy job by providing workspace ID and copy job ID. Use to verify status, review configuration, or troubleshoot failures in Microsoft Fabric.

Instructions

Get details of a specific copy 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": {
      "workspaceId": "<workspaceId>",
      "copyJobId": "<copyJobId>"
    },
    "name": "copy_job_get"
  }
}

Input Schema

Name	Required	Description	Default
`copyJobId`	Yes	The copy job ID
`workspaceId`	Yes	The workspace ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds little behavioral context beyond the operation name, and it does not mention return format, error behavior, or any other runtime traits.

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 clear sentence with no filler. It is appropriately front-loaded and conveys the essential operation in the fewest necessary words.

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?

For a simple read operation with fully documented parameters and safe annotations, the description is minimally adequate. However, with no output schema, the return content is unspecified, and the ambiguity against copy_job_get_definition leaves a gap in completeness.

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%: both copyJobId and workspaceId are described in the schema. The description adds no additional parameter meaning beyond 'specific', so the baseline score of 3 applies.

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 states a clear verb ('Get') and resource ('details of a specific copy job'), and the singular 'specific' distinguishes it from list operations like copy_job_list. However, it does not differentiate from the sibling copy_job_get_definition, since 'details' and 'definition' overlap.

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?

There is no guidance on when to use this tool versus alternatives such as copy_job_list or copy_job_get_definition. The context signals and sibling list imply usage, but the description itself provides no explicit selection criteria or exclusions.

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

Deploy Server