mcp-fabric-api

external_data_share_create

Create an external data share for an item by specifying workspace ID, item ID, paths, and recipient email to grant access to selected data.

Instructions

Create a new external data share for an item

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>",
      "itemId": "<itemId>",
      "paths": "<paths>",
      "recipientUserPrincipalName": "<recipientUserPrincipalName>"
    },
    "name": "external_data_share_create"
  }
}

Input Schema

Name	Required	Description
`paths`	Yes	Array of paths to share externally
`itemId`	Yes	The item ID
`workspaceId`	Yes	The workspace ID
`recipientUserPrincipalName`	Yes	User principal name of the recipient (email)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, establishing that this is a mutating but non-destructive operation. The description adds no further behavioral context such as permissions required, share lifecycle implications, or side effects, but it does not contradict the annotations.

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, front-loaded sentence that directly states the action and resource. It contains no filler, redundant qualifiers, or unnecessary detail.

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 create operation with four flat, fully documented parameters, the description plus schema is minimally sufficient for invocation. However, it does not explain what an external data share is, what item types support it, or what kind of result the agent should expect, leaving some conceptual ambiguity.

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?

The input schema has 100% coverage and documents all four parameters: paths, itemId, workspaceId, and recipientUserPrincipalName. The description adds no additional parameter-level semantics beyond the schema, so the baseline score of 3 is appropriate.

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?

The description uses the specific verb 'Create' with the resource 'external data share' and the object 'an item', clearly identifying the operation. This also distinguishes it from sibling tools like external_data_share_list, external_data_share_get, and external_data_share_revoke.

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 is provided about when to use this tool versus related external data share operations such as listing, getting, or revoking shares. There is also no mention of prerequisites, item type compatibility, or situations where this tool should not be used.

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

Deploy Server