Skip to main content
Glama

Affilio Link Tools

by link.affilio.mcp

Auth.Update Link

auth.update_link

Update an existing affiliate link's title, destination URL, or labels.

Provide any combination of title, target, and labels. Fields omitted from the call are left unchanged (partial update). Labels are replaced entirely — pass the full desired label set, not a delta.

Returns the updated link object on success. Requires Bearer token authentication.

Technical reference: https://affilio.link/blog/mcp-for-everyone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew human-readable title for the link. Omit to leave unchanged.
labelsNoComma-separated list of label names to assign to this link — e.g. 'summer-sale,featured'. This REPLACES all existing labels (not a merge). Pass an empty string to clear all labels. Omit to leave labels unchanged.
targetNoNew destination URL — the URL visitors land on after clicking the short link. Omit to leave unchanged.
link_idYesLink ID returned by auth.create_link or auth.list_links.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / link_id / description
      Previous value: -"Unique link ID (MongoDB ObjectId string) of the link to update. Retrieve via auth.list_links or from the create response."New value: +"Link ID returned by auth.create_link or auth.list_links."
  2. Changed4 schema fields changed
    • addedInput schema / properties / labels / description
      Added value: +"Comma-separated list of label names to assign to this link — e.g. 'summer-sale,featured'. This REPLACES all existing labels (not a merge). Pass an empty string to clear all labels. Omit to leave labels unchanged."
    • addedInput schema / properties / link_id / description
      Added value: +"Unique link ID (MongoDB ObjectId string) of the link to update. Retrieve via auth.list_links or from the create response."
    • addedInput schema / properties / target / description
      Added value: +"New destination URL — the URL visitors land on after clicking the short link. Omit to leave unchanged."
    • addedInput schema / properties / title / description
      Added value: +"New human-readable title for the link. Omit to leave unchanged."
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses partial-update semantics, full replacement of labels, the return value ('Returns the updated link object on success'), and authentication requirements ('Requires Bearer token authentication'). This is strong transparency for a mutation tool.

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 compact and front-loaded with the action and resource. Every sentence earns its place: partial-update semantics, label replacement, return value, auth, and a reference link. No filler or redundant restatement of the tool name.

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?

Given the tool's moderate complexity and the presence of an output schema, the description covers the critical invocation details: partial updates, label replacement, auth, and success return. It is slightly incomplete in that it does not guide the agent toward sibling update-like tools (e.g., set_link_visibility), but nothing needed to call this specific tool 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%, and the schema already documents that omitted fields are unchanged and labels replace existing values. The description adds global partial-update framing and the return behavior, but does not substantially add parameter-level meaning beyond the schema, so it stays at the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Update an existing affiliate link's title, destination URL, or labels.' It clearly identifies the scope of the operation. It does not explicitly differentiate from sibling tools like auth.set_link_visibility or auth.archive_link, but the field list makes the purpose unambiguous.

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 context: 'Fields omitted from the call are left unchanged (partial update)' and 'Labels are replaced entirely — pass the full desired label set, not a delta.' This tells the agent how to call it correctly. It does not explicitly state when to prefer a sibling tool, so it misses the exclusion/alternative guidance needed for a 5.

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 toolsInspect
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