storelift-mcp

create_share_link

Generate a public, read-only dashboard link for one app and storefront, with frozen data and expiration after a set number of days.

Instructions

PREVIEW ONLY: create a public, read-only link to one app's dashboard for one storefront. The link freezes the data at creation time and expires after the given number of days. Apply with confirm_action after the user approves.

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": {
      "appId": "<appId>",
      "country": "<country>"
    },
    "name": "create_share_link"
  }
}

Input Schema

Name	Required	Description
`days`	No	1-30, defaults to 7
`appId`	Yes
`country`	Yes	two-letter storefront
`password`	No	optional password for the link

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.0Oct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds real behavioral context beyond them: the link is public and read-only, freezes data at creation time, and expires after the given number of days, plus the confirm_action approval gate. Missing details on how the preview state is later applied, so not a 5.

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?

Three tight sentences with zero waste; the PREVIEW ONLY warning and confirm_action gate are front-loaded, and each clause adds a distinct constraint.

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?

For a creation tool with no output schema, the description covers the safety profile, lifecycle (freeze/expiry), and the required approval step. It leaves the return value and how the preview is committed somewhat implicit, but the confirm_action routing compensates well.

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 75% and already documents 'days' and 'country'. The description reinforces that 'days' controls expiry but adds no format or syntax detail for 'days' (e.g. 1-30 range), 'appId', or 'password' 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 ('create a public, read-only link to one app's dashboard for one storefront') and adds distinguishing scope ('PREVIEW ONLY', single app, single storefront). An agent can distinguish this from siblings like export_data or confirm_action without inspecting schemas.

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?

Clearly signals the workflow: this is a preview and must be 'Apply with confirm_action after the user approves', naming the exact sibling to route to and the approval precondition. It doesn't cover explicit when-not-to-use cases or alternatives, so it falls just short of a 5.

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

Deploy Server