AWSYS Links

Import Links from Bitly

import_from_provider

Start an asynchronous migration import from a third-party URL shortener (currently Bitly). You provide the user's Generic Access Token from the provider; awsys.co fetches their links and writes equivalent short codes in their account. Returns a jobId immediately — the job runs in the background; its progress is available by job ID. Available on Pro plans and higher, including the Pro trial (same as the REST endpoint POST /api/imports). Free-tier users receive a plan error.

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": {
      "provider": "<provider>",
      "access_token": "<access_token>"
    },
    "name": "import_from_provider"
  }
}

Input Schema

Name	Required	Description
`provider`	Yes	Source provider. Currently only "bitly" is supported.
`scan_only`	No	If true, count what would be imported without writing any short codes. Default: false.
`access_token`	Yes	Provider Generic Access Token. For Bitly: 32+ hex chars from Settings → API → Generic Access Token.
`target_namespace`	No	Optional awsys.co branded namespace prefix to land the imports under. Default: user's main namespace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only say readOnly=false, openWorld=true, idempotent=false, destructive=false; the description goes well beyond that by disclosing the asynchronous job model, that a jobId is returned immediately while work continues in the background, that short codes are actually written to the account, and that plan gating produces an error rather than a silent no-op. Those are exactly the traits an agent needs to plan a call and a follow-up.

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?

Four sentences, front-loaded with the action and its async nature, then credential source, then return value, then plan gating. Every sentence contributes new information with no repetition of the schema or annotations.

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?

There is no output schema, and the description compensates by stating the return value (jobId) and how progress is retrieved. Combined with the plan restriction, token requirement, and background-execution note, nothing an agent needs to invoke this correctly is missing.

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%, so every parameter is already documented, and the description only restates that the caller supplies the provider access token. It adds no meaning beyond the schema for scan_only (dry-run counting) or target_namespace, so the 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 — 'start an asynchronous migration import from a third-party URL shortener (currently Bitly)' — plus the concrete effect of fetching links and writing equivalent short codes. This clearly separates it from siblings like bulk_shorten (manual creation) and export_links (outbound transfer).

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 clear context: requires the user's provider token, is available on Pro plans and higher including the Pro trial, and free-tier callers get a plan error. It does not name the follow-up siblings (get_import_status, cancel_import) even though it references checking progress by job ID, nor does it say when to prefer scan_only vs. a real import — so it stops short of explicit alternatives.

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

All AWSYS Links 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?