Skip to main content
Glama

Affilio Link Tools

by link.affilio.mcp
OverviewDiscussionsAdmin

Auth.Update Store

auth.update_store

Update your Affilio storefront's metadata.

Provide any combination of name, description, and layout — fields omitted are left unchanged. For full branding updates (colors, logo, custom fonts, banner image, favicon, footer text, embedded snippet) use the Affilio dashboard → Storefront settings.

Requires Bearer token authentication.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew display name for the store. Omit to leave unchanged.
layoutNoProduct display layout. Accepted values: 'left' (sidebar layout) / 'top' (horizontal top-bar layout) / 'grid' (default card grid layout). Omit to leave unchanged.
descriptionNoNew store description shown to storefront visitors. Supports plain text. Omit to leave unchanged.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / layout / description
      Previous value: -"Product display layout. Accepted values: 'grid' (default card grid layout) or 'list' (vertical list view). Omit to leave unchanged."New value: +"Product display layout. Accepted values: 'left' (sidebar layout) / 'top' (horizontal top-bar layout) / 'grid' (default card grid layout). Omit to leave unchanged."
  2. Changed2 schema fields changed
    • removedInput schema / properties / store_id
      Removed value: -{
-  "description": "Unique store ID (MongoDB ObjectId string) of the storefront to update.",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "store_id"
-]
  3. Changed4 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"New store description shown to storefront visitors. Supports plain text. Omit to leave unchanged."
    • addedInput schema / properties / layout / description
      Added value: +"Product display layout. Accepted values: 'grid' (default card grid layout) or 'list' (vertical list view). Omit to leave unchanged."
    • addedInput schema / properties / name / description
      Added value: +"New display name for the store. Omit to leave unchanged."
    • addedInput schema / properties / store_id / description
      Added value: +"Unique store ID (MongoDB ObjectId string) of the storefront to update."
  4. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose Bearer token authentication and the partial-update contract ('fields omitted are left unchanged'), which is valuable. It says nothing about reversibility, error behavior, or whether the name is unique/validated, leaving real gaps 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then the partial-update rule, then the out-of-scope routing, then auth. Efficient overall, though the marketing 'Technical reference' blog URL adds little for an agent deciding how to call the tool.

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?

An output schema exists, so return values need not be explained, and the description covers scope, partial-update semantics, auth, and the out-of-scope branding case. Only error/validation behavior is unaddressed, which is a minor gap for a low-complexity 3-param update.

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%, with per-parameter descriptions including the accepted layout values, so the schema already does the heavy lifting. The description's only added value is the 'any combination / omitted means unchanged' framing, which is a baseline-3 contribution.

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?

States a specific verb+resource ('Update your Affilio storefront's metadata') and enumerates exactly which fields are in scope, which lets an agent distinguish it from auth.get_store and the product/link tools. It does not name a sibling explicitly, so it stops short of a 5.

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 for use ('provide any combination of name, description, layout') and an explicit when-not: full branding updates must go through the Affilio dashboard → Storefront settings. No alternative MCP tool is named, but the exclusion is concrete and actionable.

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