Skip to main content
Glama

sales_bio_link

Idempotent

A post's tracked link to put in a bio, a story sticker or a comment, where the post's own text has no clickable link (TikTok and Instagram captions). Free. Visits through it count as clicks of that post, and orders after a visit are matched to it on the Sales page. The same post and page give the same link again. Pass the "id" of the post (list your posts, or a postId from sales_overview) and, to send people to a product, a page of the owner's store as destination (default: the store's home page). It needs a connected store and a destination on the store's address. Links to the store written in a new post's text are tracked by themselves: no need to call this for them.

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": {
      "postId": "<postId>"
    },
    "name": "sales_bio_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe "id" of the post
destinationNoA page of the owner's store, e.g. a product (default: the store's home page)

Output Schema

NameRequiredDescriptionDefault
urlNo
errorNo
postIdNo
destinationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses cost ("Free"), a required account precondition (connected store), and the downstream consequences: visits count as clicks of that post and resulting orders are attributed to it on the Sales page. Its idempotency statement slightly restates idempotentHint=true, but it adds the useful specificity that the same post/page pair yields the identical existing link rather than minting a new one. No rate limits or failure modes are covered, which keeps it short of 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.

Conciseness4/5

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

The first line front-loads the purpose and the free-of-charge note, followed by attribution behavior, parameter guidance, and the exclusion case. It is somewhat long and wrapped across several lines, but each sentence carries distinct operational information, so little is wasted.

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?

Given a two-parameter tool with full schema coverage and an output schema covering the returned link, the description supplies everything an agent still needs: motivation, prerequisites, id sourcing, defaults, attribution semantics, and the case where the tool is unnecessary. Nothing material about calling it correctly is left out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3, but the description adds genuine meaning: it tells the agent where postId values come from (posts list or sales_overview) and clarifies that destination should be a product page within the owner's store while defaulting to the store home page. That sourcing guidance is not present in the schema.

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 names a specific resource — a tracked link for one post, meant for a bio, story sticker or comment — and scopes it to platforms where captions aren't clickable (TikTok, Instagram). It also implicitly separates itself from the automatic tracking of links written in a post's own text, so an agent can tell why it needs this tool rather than relying on the post body. The only weakness is that the verb is noun-phrased ("A post's tracked link") rather than an explicit "create/get", though the later line about the same post and page returning the same link makes the fetch-or-create behavior clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states both when to use it (when the post's own text has no clickable link, as on TikTok and Instagram) and when not to (links written into a new post's text are tracked by themselves, so no call is needed). It also names concrete ways to source the required id — listing posts or taking a postId from sales_overview — and states the prerequisite of a connected store plus a destination on the store's address.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources