Skip to main content
Glama

graph_resolve_share_link

Resolve a Microsoft Graph sharing link to the file or folder it points to; returns a short-lived download URL and drive ID for other file tools.

Instructions

Resolve a sharing link to the file or folder it points to.

The response carries a short-lived '@microsoft.graph.downloadUrl' that needs no Authorization header, plus the 'parentReference.driveId' to pass as drive_id to the other file tools.

Args: share_url: The sharing URL to resolve.

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": {
      "share_url": "<share_url>"
    },
    "name": "graph_resolve_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses that the response includes a short-lived '@microsoft.graph.downloadUrl' needing no Authorization header and a driveId for downstream tools, but it omits whether the resolve call itself has side effects, required permissions, or error behavior.

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 front-loaded with purpose, then follows with the important response fields and the one argument. Every line contributes useful information, and there is no unnecessary wording.

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 simple one-parameter resolver with no output schema, the description covers purpose, key response values, and how the result feeds other tools. It leaves out auth requirements and failure modes, but the invocation-critical details are present.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the single parameter. It only restates 'share_url' as 'The sharing URL to resolve' without specifying accepted URL formats, encoding expectations, or examples, adding little beyond the parameter name.

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 states a specific verb and resource: 'Resolve a sharing link to the file or folder it points to.' It clearly distinguishes this direction of share-link handling from share creation tools such as graph_share_file, so an agent can identify the tool without opening 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?

The description gives clear downstream context: use the returned parentReference.driveId as drive_id with other file tools. It does not explicitly state when not to use this tool or name alternative approaches, but the usage context is specific enough for a simple resolver.

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

Deploy Server

Other Tools