Affilio Link Tools

Check Url

check_url

Check the health and destination of a URL (link checker / redirect resolver).

Follows the redirect chain, returns the final resolved URL, HTTP status codes, page title, and — for Amazon and AliExpress product pages — whether the product is still available (in stock / not deleted).

Use this tool when the user needs to:

Verify an affiliate or product link still works (not broken / 404 / dead)
Resolve where a short or redirecting link actually lands
Check whether an Amazon/AliExpress product is still available
Inspect the redirect chain of a URL

Returns: finalUrl (str): The final URL after following all redirects title (str): The destination page's title (or empty string) redirectChain (list[str]): URLs visited, in order responseCode (str): Final HTTP status code (e.g. "200", "404") lastRedirectResponseCode (str): Status of the last redirect hop, if any available (bool | null): True/False for Amazon/AliExpress product pages, null when availability is not applicable

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Full HTTP/HTTPS URL to health-check. The tool follows redirects, reports the final URL and HTTP status, extracts the page title, and detects Amazon/AliExpress product availability. Example: https://www.amazon.com/dp/B08N5WRWNW

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedJul 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It transparently explains that the tool follows redirect chains, returns HTTP status codes, extracts page titles, and detects availability only for Amazon/AliExpress product pages. This goes well beyond the input schema, though it does not mention potential external network behavior or side effects.

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?

The description is well organized with a clear summary, a use-case bullet list, and a return-value block. It is slightly verbose because the return fields are also present in the output schema, but the structure makes the information easy to scan and act on.

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?

For a single-parameter tool with an output schema, the description is complete: it explains the tool's purpose, what it follows and returns, when to use it, and the special availability behavior for Amazon/AliExpress. Nothing essential for invoking or interpreting the tool 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 coverage is 100% and the single parameter is already well documented in the schema. The description adds behavioral context but no additional parameter-specific semantics beyond what the schema provides. Baseline 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?

States a specific verb and resource: 'Check the health and destination of a URL (link checker / redirect resolver).' It clearly names what the tool does and distinguishes it from sibling tools like shorten_url, generate_qr, and check_international_redirect by focusing on health checking and redirect resolution.

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?

Provides an explicit bulleted list of when to use the tool: verifying affiliate/product links, resolving short links, checking Amazon/AliExpress availability, and inspecting redirect chains. It does not explicitly name alternatives or when-not-to-use conditions, but the use cases are clear enough for an agent to select it correctly.

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

All Affilio Link Tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools map cleanly to distinct resources and actions, but auth.create_link vs shorten_url and check_url vs check_international_redirect have overlapping purposes. The descriptions do a good job of clarifying the differences, so ambiguity is limited.

Naming Consistency4/5

All names follow a readable snake_case verb_noun pattern, but auth.* tools are prefixed while utility tools like check_url, generate_qr, and shorten_url are not. Names like list_links and list_links_ranked are also close, though still predictable.

Tool Count3/5

20 tools is on the heavy side for this domain. Most cover distinct functions, but there is some redundancy such as list_links_ranked being a sorting variant of list_links and shorten_url overlapping with auth.create_link.

Completeness3/5

Link lifecycle coverage is solid: create, get, list, update, archive, stats, and visibility are all present. However, product management is incomplete with no update/delete/remove-link operations, and there is no unarchive or hard-delete for links.

Resources

Need Help?