Sharelint

Check app links

check_app_links

Read-onlyIdempotent

Check whether a URL opens the site’s iOS or Android app instead of the browser. Validates apple-app-site-association (iOS Universal Links) and assetlinks.json (Android App Links), tests this exact URL against the iOS path rules, and compares the files with the copies Apple’s CDN and Google’s Digital Asset Links service have cached. Returns status per platform and copy-ready fixes. Use it when Universal Links or App Links do not work.

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": {
      "url": "<url>"
    },
    "name": "check_app_links"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL or bare domain to check, for example "example.com/pricing". Private and local addresses are refused.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real substance beyond that: it discloses that it fetches association files, tests the exact URL against iOS path rules, and diffs against Apple/Google cached copies — non-obvious network behavior. It omits latency/rate considerations for those external fetches.

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 purpose, then the mechanism, then the return value and usage cue. It is a single dense sentence whose clauses all carry information, though the run of parallel verbs makes it slightly heavy to parse at a glance.

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?

No output schema exists, and the description compensates by stating what comes back — per-platform status plus copy-ready fixes. Combined with the disclosed checks and the annotation-covered safety profile, an agent has everything needed to select and call it.

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?

With a single parameter at 100% schema coverage, the schema already defines the input fully. The description's 'tests this exact URL' adds slight meaning about how the URL is consumed (per-path matching rather than domain-level), but no format or edge-case detail beyond the schema.

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 — checking whether a URL opens an iOS/Android app instead of the browser — and names the exact artifacts it inspects (apple-app-site-association, assetlinks.json). This scope is clearly separable from sibling tools like check_url or check_link_preview.

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 a clear triggering condition: 'Use it when Universal Links or App Links do not work.' It does not, however, explicitly exclude adjacent cases (e.g., plain redirect or preview issues) or name which sibling to use instead for those.

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

All Sharelint 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?